Thanks, I will try to fix the reverse addressess ... thanks.
On 11/15/05, Bryan Whitehead <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] ~]$ dig -x 210.200.1.1 | grep AUTHORITY\ SEC -A 1
> ;; AUTHORITY SECTION:
> 1.200.210.in-addr.arpa. 10733 IN SOA dns.ht.net.tw.
> root.dns.ht.net.tw.
[EMAIL PROTECTED] ~]$ dig -x 210.200.1.1 | grep AUTHORITY\ SEC -A 1
;; AUTHORITY SECTION:
1.200.210.in-addr.arpa. 10733 IN SOA dns.ht.net.tw.
root.dns.ht.net.tw. 1999090230 10800 3600 360 86400
Are you dns.ht.net.tw. ??? If not, then you need to contact them to get
the reverse f
On 14 November 2005 17:46, Allan Spagnol Comar wrote:
> Hi All, I am having a little problem with my DNS server; I using a DNS
> server at 210.200.1.230;
> when I do nslookup dnsserver.com.br it returns 210.200.1.230
> when I try nslookup 192.168.0.2 it return ** server can't find
> 230.1.200.210.i
still the problem
[EMAIL PROTECTED] ~ $ host 210.200.1.230
Host 230.1.200.210.in-addr.arpa not found: 3(NXDOMAIN)
[EMAIL PROTECTED] ~ $ host 210.200.1.232
232.1.200.210.in-addr.arpa domain name pointer shakan.commodity.com.br.
and seems to me that both shakan.eng.com.br and thewho.eng.com.br is
c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2005-11-14 12:46 -0300, [EMAIL PROTECTED] wrote:
> does someone have a clue about what is going on ?
Yes, `nslookup' is fundamentally broken. Try `host' or `dig' (with its
`-x' option) instead.
And don't expect RFC 1918 address space to be resolva
Hi All, I am having a little problem with my DNS server; I using a DNS
server at 210.200.1.230;
when I do nslookup dnsserver.com.br it returns 210.200.1.230
when I try nslookup 192.168.0.2 it return ** server can't find
230.1.200.210.in-addr.arpa: NXDOMAIN
does someone have a clue about what is go
6 matches
Mail list logo
