Sam Varshavchik wrote: > It's there; it's been working fine for me for the last couple of days. > > courier.bynari.net. 72278 IN A 12.96.164.244 > bynari.net. 70757 IN NS ns1.theplanet.com. > bynari.net. 70757 IN NS ns2.theplanet.com. > > It does appear that a few people are running into some unknown glitch > resolving the domain. One of those people turned out to be their > president, so they know about this, and are trying to figure out what's > going on.
The NS set provided by the GTLD servers and one of the glue nameservers is different from the NS set provided by the other glue nameserver. The glue records point to ns.bynari.net and ns1.theplanet.com. The NS records on ns.bynari.net (aka courier.bynari.net aka www.bynari.net aka relay.bynari.net aka req2.bynari.net) agree with the glue records. ns1.theplanet.com, though, claims that it and ns2.theplanet.com are authoritative. This kind of situation, unless watched closely (and if you know enough to watch it closely, why let it stand?), can lead to the error we've been seeing, where some people can resolve the new record and some can't. Either the NS set on ns1.theplanet.com needs to be updated to jive with ns.bynari.net or, more likely, the glue records need to be updated with bynari's registrar (Network Solutions). HTH, pete ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
