> The rest of the internet appears to have figured out the forward and
> reverse lookups for
>
> ns1.sysadmin-inc.com <--> 209.16.228.145
>
> but eventhough hub.freebsd.org knows
> 209.16.228.145 --> ns1.sysadmin-inc.com
>
> It's still under the incorrect assumption (for the past two weeks or more)
> that:
> ns1.sysadmin-inc.com --> 209.16.228.150
>
> Could someone please bump that system and have it update the cache.?...
The problem isn't hub.freebsd.org or its name servers. The problem is
the .com name servers which have a glue record for ns1.sysadmin-inc.com:
% dig ns sysadmin-inc.com @b.gtld-servers.net
; <<>> DiG 8.3 <<>> ns sysadmin-inc.com @b.gtld-servers.net
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 4
;; QUERY SECTION:
;; sysadmin-inc.com, type = NS, class = IN
;; ANSWER SECTION:
sysadmin-inc.com. 2D IN NS NS2.DELTACOM.NET.
sysadmin-inc.com. 2D IN NS NS1.DELTACOM.NET.
sysadmin-inc.com. 2D IN NS NS1.sysadmin-inc.com.
sysadmin-inc.com. 2D IN NS VIRTUAL.sysadmin-inc.com.
;; ADDITIONAL SECTION:
NS2.DELTACOM.NET. 2D IN A 207.230.75.50
NS1.DELTACOM.NET. 2D IN A 207.230.75.34
NS1.sysadmin-inc.com. 2D IN A 209.16.228.150
VIRTUAL.sysadmin-inc.com. 2D IN A 209.16.228.140
Until this glue record is corrected, you *will* have problems with the
rest of the net.
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
