• April 13, 2025, 02:14:37 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Local Domain Name DNS Setting  (Read 8311 times)

booglehead

  • Level 1 Member
  • *
  • Posts: 12
Local Domain Name DNS Setting
« on: November 20, 2007, 10:41:32 AM »

Hello all,

I just recently switched from a linksys router and was extermly use to the local domain name dns feature (DNSMasq). I don't understand the DNS settings of this new router [DIR-655]. I have tried all sorts of settings. For instance,

I set the local domain name which shows corectly on my Windows machines under the value of "connection-specific DNS suffix"  but when I try to ping short names for other Windows hosts on the same subnet the reply is always short name. When I try to resolve to shortname.localdnsname it never resolves. I can't even connect to the "Gateway Name" value I specified. Can anyone help with this annoying sitution? Thanks.

Logged

JHK

  • Level 3 Member
  • ***
  • Posts: 136
Re: Local Domain Name DNS Setting
« Reply #1 on: November 27, 2007, 06:00:29 PM »

Use the nslookup and see if you are getting the full domain. Reply with the outcome. The NetBT loaded on the local machine?
Logged
Life is cool! :)

booglehead

  • Level 1 Member
  • *
  • Posts: 12
Re: Local Domain Name DNS Setting
« Reply #2 on: December 02, 2007, 10:23:35 AM »

Use the nslookup and see if you are getting the full domain. Reply with the outcome.

C:\Users\booglehead>nslookup tiger
Server:  UnKnown
Address:  192.168.0.1:53

*** UnKnown can't find tiger: Non-existent domain

C:\Users\booglehead>nslookup cheetah
Server:  UnKnown
Address:  192.168.0.1:53

*** UnKnown can't find cheetah: Non-existent domain

The NetBT loaded on the local machine?

I assume your asking if NetBT is routing NetBIOS on the local machine. The answer is no. I've explicitly disable NetBIOS over TCP/IP. I opted for using FQDN's on my local lan. Does the D-Link even support this? So far, all signs are pointing to no.

I would hate to enable/run NetBIOS again; its slow (another filter on top of the TCP/IP stack) and ancient technology. Any other suggestions I can try --or is this a bug/issue in the latest 1.10 firmware? Thanks.
Logged