Somebody somewhere is lying to me about how DNS works

Post #204,766 by FuManChu 4/25/05 1:44:10 PM Reply	Somebody somewhere is lying to me about how DNS works C:\\>ipconfig /flushdns\n\nWindows 2000 IP Configuration\n\nSuccessfully flushed the DNS Resolver Cache.\n\nC:\\>nbtstat -R\n Successful purge and preload of the NBT Remote Cache Name Table.\n\nC:\\>nslookup www.casadeamor.com\nServer: chilly-willy.amorhq.net\nAddress: 192.168.0.2\n\nName: www.casadeamor.com\nAddress: 192.168.0.19\n\n\nC:\\>ping www.casadeamor.com\n\nPinging www.casadeamor.com [64.73.226.28] with 32 bytes of data:\n\nRequest timed out.\nRequest timed out.\nRequest timed out.\nRequest timed out.\n\nPing statistics for 64.73.226.28:\n Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),\nApproximate round trip times in milli-seconds:\n Minimum = 0ms, Maximum = 0ms, Average = 0ms\n\nC:\\>ipconfig /all\n\nWindows 2000 IP Configuration\n\n Host Name . . . . . . . . . . . . : REDROVER\n Primary DNS Suffix . . . . . . . : HQAMOR.amorhq.net\n Node Type . . . . . . . . . . . . : Hybrid\n IP Routing Enabled. . . . . . . . : No\n WINS Proxy Enabled. . . . . . . . : No\n DNS Suffix Search List. . . . . . : HQAMOR.amorhq.net\n amorhq.net\n\nEthernet adapter my-tap:\n\n Media State . . . . . . . . . . . : Cable Disconnected\n Description . . . . . . . . . . . : TAP-Win32 Adapter V8\n Physical Address. . . . . . . . . : 00-FF-05-6E-64-CC\n\nEthernet adapter Wireless:\n\n Connection-specific DNS Suffix . : HQAMOR.amorhq.net\n Description . . . . . . . . . . . : LAN-Express IEEE 802.11 PCI Adapter\n Physical Address. . . . . . . . . : 00-02-8A-94-E2-C4\n DHCP Enabled. . . . . . . . . . . : Yes\n Autoconfiguration Enabled . . . . : Yes\n IP Address. . . . . . . . . . . . : 192.168.0.74\n Subnet Mask . . . . . . . . . . . : 255.255.255.0\n Default Gateway . . . . . . . . . : 192.168.0.110\n DHCP Server . . . . . . . . . . . : 192.168.0.2\n DNS Servers . . . . . . . . . . . : 192.168.0.2\n 216.70.224.17\n 216.70.224.18\n Lease Obtained. . . . . . . . . . : Monday, April 25, 2005 9:24:03 AM\n Lease Expires . . . . . . . . . . : Tuesday, May 03, 2005 9:24:03 AM\n\nEthernet adapter Local Area Connection 2:\n\n Media State . . . . . . . . . . . : Cable Disconnected\n Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection\n Physical Address. . . . . . . . . : 08-00-46-AD-24-30\n\nC:\\> I don't get it. Where is the 64.73.226.28 address coming from? My hosts and lmhosts files are empty. If I `ipconfig /renew` my IP, I sometimes get ping to work. But not always. Heavy sigh.
Post #204,783 by folkert 4/25/05 2:37:47 PM Reply	Welp... In you stuff posted, I don't see your DNS server's entry. Are you using Windows DNS services or are you using a UNIX machine as your DNS server? [greg@king:~]$ dig www.casadeamor.com\n\n; <<>> DiG 9.3.1 <<>> www.casadeamor.com\n;; global options: printcmd\n;; Got answer:\n;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56477\n;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0\n\n;; QUESTION SECTION:\n;www.casadeamor.com. IN A\n\n;; ANSWER SECTION:\nwww.casadeamor.com. 3600 IN A 64.73.226.28\n\n;; AUTHORITY SECTION:\ncasadeamor.com. 3600 IN NS ns1.domaindiscover.com.\ncasadeamor.com. 3600 IN NS ns2.domaindiscover.com.\n\n;; Query time: 182 msec\n;; SERVER: 192.168.1.90#53(192.168.1.90)\n;; WHEN: Mon Apr 25 14:34:35 2005\n;; MSG SIZE rcvd: 103\n\n[greg@king:~]$\n I hope that answers it for you. -- [link\|mailto:greg@gregfolkert.net\|greg], [link\|http://www.iwethey.org/ed_curry\|REMEMBER ED CURRY!] @ *i_wethey* [image\|http://www.danasoft.com/vipersig.jpg\|\|\|\|]
Post #204,784 by FuManChu 4/25/05 3:00:00 PM Reply	Windows DNS server, but internally only. 192.168.0.2 is a Windows DNS server, running on my local private subnet. I want lookups for casadeamor.com to resolve to 192.168.0.19 when I'm on the same subnet, but resolve to 64.73.226.28 when I'm somewhere elese on the 'Net. It almost works.
Post #204,792 by dws 4/25/05 4:02:20 PM Reply	Re: Windows DNS server, but internally only. I recall a problem with Win2K losing the first DNS server, and falling back on the secondary. This drove us nuts for quite a while at work, since desktops would stop resolving stuff on the local net, but could resolve names in the outside world. I think that we resolved the problem by adding a second internal DNS server, so that losing the first was benign. At the time (~3 year back) there was chatter on the net about the problem, but no acknowledgement from Microsoft.
Post #204,806 by FuManChu 4/25/05 5:18:50 PM Reply	Thanks. Was that the client "losing the first DNS server"? If so, maybe a dummy IP (for the second DNS server) would fix it.
Post #204,808 by dws 4/25/05 5:39:44 PM Reply	Yup. Win2K client was losing first DNS entry The DNS server happened to also be Win2K, though that appeared to be unrelated to the client problem.
Post #204,811 by drewk 4/25/05 7:42:27 PM Reply	Sounds familiar We had to set up two nameservers at work, too. Sorry, nothing useful, just a Me Too. === Purveyor of Doc Hope's [link\|http://DocHope.com\|fresh-baked dog biscuits and pet treats]. [link\|http://DocHope.com\|http://DocHope.com]

Welcome to IWETHEY!