> -----Original Message----- > From: Larry Brown > Sent: Sunday, March 30, 2003 5:18 PM > Subject: RE: NameServer, DNS, and BIND > > > According to whois, the domain name servers responsible for > mystyka.com are out of hostsave.com. Their nameservers are > resolving your domain name to an address on their network. > So your bind installation is mute to anyone not using your > bind server as their dns. You need to change the dns servers > listed with your registrar to show the ip address of your > name server or you need to access the dns servers at > hostsave.com and put entries in for your mail and www. > machine etc.
I would agree with your mute point if the whois servers were actually queried, but the whois servers are databases and are not queried by DNS. Plus, the whois servers are typically updated after the tld servers are updated. At least thats been my experienace when I make a change to any of my name server records. Sometimes it takes 24-48 hours for the whois servers to catchup. With regards to this post - using dig's trace mode... +[no]trace Toggle tracing of the delegation path from the root name servers for the name being looked up. Tracing is disabled by default. When tracing is enabled, dig makes iterative queries to resolve the name being looked up. It will follow referrals from the root servers, showing the answer from each server that was used to resolve the lookup. [EMAIL PROTECTED] scowles]$ dig +trace mystyka.com ns ; <<>> DiG 9.2.1 <<>> +trace mystyka.com ns ;; global options: printcmd . 517987 IN NS E.ROOT-SERVERS.NET. . 517987 IN NS F.ROOT-SERVERS.NET. . 517987 IN NS G.ROOT-SERVERS.NET. . 517987 IN NS H.ROOT-SERVERS.NET. . 517987 IN NS I.ROOT-SERVERS.NET. . 517987 IN NS J.ROOT-SERVERS.NET. . 517987 IN NS K.ROOT-SERVERS.NET. . 517987 IN NS L.ROOT-SERVERS.NET. . 517987 IN NS M.ROOT-SERVERS.NET. . 517987 IN NS A.ROOT-SERVERS.NET. . 517987 IN NS B.ROOT-SERVERS.NET. . 517987 IN NS C.ROOT-SERVERS.NET. . 517987 IN NS D.ROOT-SERVERS.NET. ;; Received 292 bytes from 127.0.0.1#53(127.0.0.1) in 11 ms com. 172800 IN NS A.GTLD-SERVERS.NET. com. 172800 IN NS B.GTLD-SERVERS.NET. com. 172800 IN NS C.GTLD-SERVERS.NET. com. 172800 IN NS D.GTLD-SERVERS.NET. com. 172800 IN NS E.GTLD-SERVERS.NET. com. 172800 IN NS F.GTLD-SERVERS.NET. com. 172800 IN NS G.GTLD-SERVERS.NET. com. 172800 IN NS H.GTLD-SERVERS.NET. com. 172800 IN NS I.GTLD-SERVERS.NET. com. 172800 IN NS J.GTLD-SERVERS.NET. com. 172800 IN NS K.GTLD-SERVERS.NET. com. 172800 IN NS L.GTLD-SERVERS.NET. com. 172800 IN NS M.GTLD-SERVERS.NET. ;; Received 461 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 130 ms mystyka.com. 172800 IN NS ns1.mystyka.com. mystyka.com. 172800 IN NS ns3.mystyka.com. ;; Received 97 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 71 ms So mystyka.com has been properly delegated at the tld's. Unfortunately, the OP is struggling with how to setup a name server to answer the delegation (SOA) to his IP address. Steve Cowles -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
