Re: NSLookup failure in DNS

Sherpa Tenzing wrote:
Setting up Reverse Lookup helped some. Now the server is resolved but
the client machine bdev is not, see below:
Default Server: bsocket.bsocketdomain.bsocket.co
Address: 192.168.0.3

bdev
Server: bsocket.bsocketdomain.bsocket.com
Address: 192.168.0.3

Non-authoritative answer:
Name: bdev.bSocket.com
Address: 68.178.232.99

ajaytablet
Server: bsocket.bsocketdomain.bsocket.com
Address: 192.168.0.3

Non-authoritative answer:
Name: ajaytablet.bSocket.com
Address: 68.178.232.99

68.178.232.99 is not a correct IP address it is totally bogus.

I wouldn't say it is exactly bogus, the problem is that bSocket.com should
not be in your DNS suffix search list. Your internal DNS is not
authoritative for it, and is resolving all queries using a wildcard record
in the public DNS.


Active Directory domain name from AD Users & Computers
bSocketDomain.bSocket.com is the name of the domain.

You can fix this on your XP and Win2k3 clients by using a group policy that
will assign "bSocketDomain.bSocket.com" as the only domain DNS suffix
searched.
Computer Configuration
-Administrative templates
-Network
-DNS Client
DNS Suffix search list


The Domain Name and prefix seem to all match. And all things yu ask
seem to match.
I am surprised this so hard to fix. Aprecaite all your help.

The clue to this is the "non-authoritative answer", it clearly points to a
wildcard record in your public domain, and it is not your local DNS server's
problem, you will get the same answer to any query in bsocket.com.

Non-authoritative answer:
Name: ajaytablet.bSocket.com
Address: 68.178.232.99

W:\>nslookup See-how-wildcard-records-cause-issues.bsocket.com. 65.65.91.213
Server: dns.wftx.us
Address: 65.65.91.213
Aliases: 213.91.65.65.in-addr.arpa

Non-authoritative answer:
Name: See-how-wildcard-records-cause-issues.bsocket.com
Address: 68.178.232.99

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


.

Relevant Pages

  • Re: sbs 2003 Clients do not have internet access
    ... Are you using a PPPoE connection? ... > Here is the ipconfig /all for the client and server ... > Connection-Spific DNS Suffix ccs.local ... >>the clients computer or all the client will not have the ability to ...
    (microsoft.public.windows.server.sbs)
  • Re: UNC paths by IP good, by name bad
    ... Win2003 servers' shares over the VPN when I specify the server by IP ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ... You may also want to check the Cisco client t make sure it is using ...
    (microsoft.public.windows.server.networking)
  • Re: DNS problems - This is driving me crazy
    ... I apologize for 192.168.0.200 as the DNS Suffix Search List. ... The statement that "The server CANNOT ping the client" is also wrong. ... Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: Clients cannot access Internet through Win 2003 SBS
    ... Both ipconfigs are looking good. ... > I've included a list of my ipconfig /all from my client and my server. ... > DNS Suffix Search List: ...
    (microsoft.public.windows.server.sbs)
  • Re: Server not responding error
    ... that w2k box in the server. ... > without DNS(in the ipconfig of the client, you can see there is DNS for ... >>> Ethernet adapter Idc Internet: ... >>> DNS suffix search list: ...
    (microsoft.public.backoffice.smallbiz2000)
Loading