Aryeh M. Friedman wrote:
Already did (went a step farther had my machine at home -CURRENT use
the one at work [the one with the probldem] as it's /etc/resolv.conf
and as a forwarder in my named.conf and both worked fine)
Forgot to mention that different ISP's so it is not a port blocking problem
Xin LI wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Aryeh M. Friedman wrote:
I have registered and pointed to my name server the following domains:
istudentunion.com (.net and .org)
They resolve locally but do not resolve remotely.... it has been 24 hrs
so some propagation should of occured... I tested resolving remotely
with hardcoding the nameserver to be me and that works... what else
should I look at... I am using the named in base 7.2-PREREALSE
(i386) and used the guidelines in O'reilly's DNS and BIND.... what
other tests
configs should I try? (I double checked the zone type and that I have
all the trailing dots)
Note I have also transfered registers in the last 24 hrs (but whois has
all the right data)
BIND by default listen on lo0 only. Check your /etc/namedb/named.conf.
- --
Xin LI <[email protected]> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAknbowcACgkQi+vbBBjt66BPRwCdE3cAE8U+3687Dl9ICDx5PIsv
6pEAn1ZCCPmEJiFw7UkM2E7ErTLvG2S5
=k1/J
-----END PGP SIGNATURE-----
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[email protected]"
