You can also ask on the SF-LUG list ... might get (at least some)
answers more quickly that way.
First, with dig, there's also question of what one's running the
queries against. One can use @ to check against a particular DNS server.
What matters most is what folks see from The Internet at large (at least
in the case of Internet web server, anyway).
One can also use the -trace option (but don't overuse/abuse it - but it
is useful to trace the delegation all the way down, when needed. Still,
however, one might occasionally need to do some manual checks along the
way - as -trace will check down just one particular (effectively randomly
selected) path of chain of delegation (among multiple possible paths)).
Also, for the specific bits other folks might not know about ... what I did
and didn't (thus far) change in DNS - I haven't (quite yet, anyway)
changed anything in Internet DNS - neither for BALUG.ORG. or SF-LUG.COM.
The only real bits I/we did yesterday (unless it's been taken further by
you or others - I presume you're working on that) was mostly minimal bits
on the relocated physical host to get it back onto the network (and
even that, mostly just concentrated on dom0 host).
Anyway, let me poke a bit more at sf-lug.com. DNS and see what I see (if
you and/or others don't already sort that out sooner than I manage to).
For those playing at home ;-) ... we have:
Silicon Mechanics, updated (moved) on 2009-11-11:
208.96.15.248/29 network #formerly 208.69.42.128/25
208.96.15.249 router #formerly 208.69.42.129
208.96.15.250 dom0 #formerly 208.69.42.165
208.96.15.251 sflug domU #formerly 208.69.42.166
208.96.15.252 balug domU #formerly 208.69.42.167
208.96.15.253 (useable)
208.96.15.254 (useable)
208.96.15.255 broadcast #formerly 208.69.42.255
sf-lug.com. was: 208.96.15.252 (that older tower system has been removed
and taken off-line)
footnote(s)/references/excerpts:
I may be (and often am) running significantly behind in reading the
sf-lug list.
dig(1)
Quoting jim <jim at well.com>:
> when i
> $ dig sf-lug.com
> i get
> 208.96.15.252 # sb 251
>> when i use a browser to access http://www.sf-lug.com> i get
>http://www.sf-lug.com/apache2-default/> which i believe is served off of the balug vm (252).
>> the name servers are listed as
> ns1.sf-lug.com
> ns2.sf-lug.com
>> $ dig ns1.sf-lug.com
> shows
> ns1.sf-lug.com. 85611 IN A 208.96.15.252
>> $ dig ns2.sf-lug.com
> shows
> ns2.sf-lug.com. 85553 IN A 198.144.195.186
>> i'm guessing that you've copied the dns info from
> the tower to the balug vm and that it is not on
> the sf-lug vm.
>> i believe the 198...186 machine is rick moen's.
>> how to update the dns servers so
>http://www.sf-lug.com> works as expected?