Search Again: Re: Panther, shared internet, and QDNS From: Len Conrad Date: Saturday, December 27, 2003 Time: 5:57:53 am >Thank you for pointing this one out to me. I find it strange that you >came up with that IP address, since that was supposedly changed last August. > >So, you found a real problem. Now, how do I go about tracking down where >it's wrong, and getting it corrected? ns3 is delegated by the .com parent NSs: # dig @a.gtld-servers.net greenbuilder.com any ; <<>> DiG 9.2.3rc3 <<>> @a.gtld-servers.net greenbuilder.com any ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53487 ;; flags: qr rd; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;greenbuilder.com. IN ANY ;; ANSWER SECTION: greenbuilder.com. 172800 IN NS ns1.greenbuilder.com. greenbuilder.com. 172800 IN NS ns2.greenbuilder.com. greenbuilder.com. 172800 IN NS ns2.one4allhosting.com. greenbuilder.com. 172800 IN NS ns3.greenbuilder.com. ;; AUTHORITY SECTION: greenbuilder.com. 172800 IN NS ns1.greenbuilder.com. greenbuilder.com. 172800 IN NS ns2.greenbuilder.com. greenbuilder.com. 172800 IN NS ns2.one4allhosting.com. greenbuilder.com. 172800 IN NS ns3.greenbuilder.com. ;; ADDITIONAL SECTION: ns1.greenbuilder.com. 172800 IN A 205.238.129.202 ns2.greenbuilder.com. 172800 IN A 205.238.129.194 ns2.one4allhosting.com. 172800 IN A 24.234.162.52 ns3.greenbuilder.com. 172800 IN A 24.234.47.110 <<<<<<<<<< As a registered host: whois ns3.greenbuilder.com Whois Server Version 1.3 Domain names in the .com and .net domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information. Server Name: NS3.GREENBUILDER.COM IP Address: 24.234.47.110 Registrar: WILD WEST DOMAINS, INC. Whois Server: whois.wildwestdomains.com Referral URL: http://www.wildwestdomains.com but there is a warning from the whois server: No match for "ns3.greenbuilder.com" in the registrar database. If that's not the IP you want (ns1 has an A record of ns3 of 24.234.162.52: # dig @ns1.greenbuilder.com. ns3.greenbuilder.com. ; <<>> DiG 9.2.3rc3 <<>> @ns1.greenbuilder.com. ns3.greenbuilder.com. ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9796 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;ns3.greenbuilder.com. IN A ;; ANSWER SECTION: ns3.greenbuilder.com. 86400 IN A 24.234.162.52 ), ... then the registrant for greenbuilder.com has to work with the registrar for greenbuilder.com to change or remove the ns3 glue record. >>2) ERROR: One or more of the nameservers listed at the parent servers are >>not listed as NS records at your nameservers. The problem NS records are: >>ns2.one4allhosting.com. > >ns2.one4allhosting.com is the same IP as ns3.greenbuilder.com (or should >be... see above). The reason for the ns3 name is simply to avoid >confusing hosting clients. "zone data must match delegation data" and "SOA mname field must be in zone NS records" >Most of them don't really need to know that we have a reciprocal DNS >agreement with one4allhosting.com, why that is of benefit to them, etc etc. If their cosmetic understanding of DNS needs to be fooled by your DNS errors, they probably don't know enough about DNS to bother with you purposely making such errors. >If there is any actual problem with this practice (assuming the host is >properly defined, of course), please let me know. There are real and subtle problems, sooner or later, when your NS records do not meet the rules of thumb above. >>mail.greenbuilder.com. and mail.greenbuilder.com. both resolve to >>205.238.129.197. > >The result of discontinuing use of a live backup mail server due to spam >relay concerns. A perfectly valid tactic, I've seen other ISPs do the same. While not optimal, there is really no harm done, esp if the IP is up and receiving. And if not, then you got higher priority problems to fix than this non-problem of two MX records having the same mail destination. Len

Messages In This Thread: Panther, shared internet, and QDNS by System Administrator on Dec 18, 2003 at 10:40:03 am Re: Panther, shared internet, and QDNS by Ron Smith on Dec 19, 2003 at 1:31:15 am Re: Panther, shared internet, and QDNS by System Administrator on Dec 19, 2003 at 4:24:01 am Re: Panther, shared internet, and QDNS by mattb on Dec 19, 2003 at 10:31:50 am Re: Panther, shared internet, and QDNS by Mia''s Virtual Post Office on Dec 22, 2003 at 10:05:05 am Re: Panther, shared internet, and QDNS by Len Conrad on Dec 22, 2003 at 10:38:43 am Re: Panther, shared internet, and QDNS by Michael Wise on Dec 22, 2003 at 11:21:16 am Re: Panther, shared internet, and QDNS by Len Conrad on Dec 22, 2003 at 5:26:48 pm Re: Panther, shared internet, and QDNS by Michael Wise on Dec 22, 2003 at 6:08:36 pm Re: Panther, shared internet, and QDNS by billc_lists@greenbuilder.com on Dec 22, 2003 at 11:20:20 pm Re: Panther, shared internet, and QDNS by Michael Wise on Dec 23, 2003 at 8:59:19 am Re: Panther, shared internet, and QDNS by Len Conrad on Dec 23, 2003 at 12:01:08 pm Re: Panther, shared internet, and QDNS by Michael Wise on Dec 23, 2003 at 4:43:54 pm Re: Panther, shared internet, and QDNS by billc_lists@greenbuilder.com on Dec 27, 2003 at 12:07:21 am Re: Panther, shared internet, and QDNS by Len Conrad on Dec 27, 2003 at 5:57:53 am Re: Panther, shared internet, and QDNS by Men & Mice Support on Dec 29, 2003 at 12:41:13 pm Re: Panther, shared internet, and QDNS by Len Conrad on Dec 29, 2003 at 2:06:31 pm Re: Panther, shared internet, and QDNS by Men & Mice Support on Dec 29, 2003 at 2:29:57 pm Re: Panther, shared internet, and QDNS by Len Conrad on Dec 29, 2003 at 2:41:06 pm Re: Panther, shared internet, and QDNS by Men & Mice Support on Dec 29, 2003 at 3:15:46 pm Re: Panther, shared internet, and QDNS by Len Conrad on Dec 29, 2003 at 6:49:52 pm Re: Panther, shared internet, and QDNS by billc_lists@greenbuilder.com on Dec 29, 2003 at 10:51:25 pm