So it is in fact possible that the source file shows "host1", etc., but it has been deleted from the zone/journal file.
[EMAIL PROTECTED] wrote:
Hi,
One issue that it might be is that your /etc/resolv.conf is pointing to
different NS, which is then populated itself with data from your secondary NS. Add your own NS to /etc/resolv.conf if you want to resolve based on your local NS.
If your secondary NS is malfunctioning or not configured to accept IXFR or AXFR, then the zone information in your two NS's will differ.
An easy way to test this misconfiguration is to use http://www.dnsreport.com, and enter your domain there. It will show any disrepancies, and also suggest fixes when your TTL etc values are skewed.
To see what particular NS's are responding with you should use the syntax:
host <domain to resolve> <server to resolve from>
This will show whether these NS's are responding correctly.
Most of this looks like bind issues, but should be easily resolved :)
Hope this helps some!
[EMAIL PROTECTED] wrote:
The zone file looks OK to me. The source files generated when BIND generates a source file for dynamic zones are pretty convoluted. Readability by human beings was clearly not one of the design goals. I think the source files are just intended to be consolidations of the journal file. And when the journal file is reloaded again from the source file (because the journal has been removed) it will be more efficiently organized.
Since this is likely some subtle issue with your BIND configuration, you may want to ask about it on the BIND list. The same applies if there actually is some problem with the BIND dynamic update support.
I don't see what the problem is. Sorry.
[EMAIL PROTECTED] wrote:
When I send the 'ping ns1.mydomain.com', it works fine.
When I send the 'ping test1.mydomain.com', it returns:
ping: unknown host test1.mydomain.com
The below is the result of 'dig mydomain.com. soa'
; <<>> DiG 9.2.1 <<>> mydomain.com. soa ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37164 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION: ;mydomain.com. IN SOA
;; ANSWER SECTION:
mydomain.com. 83298 IN SOA ns1.mydomain.com. root.mydomain.com. 20030821 10800 3600 604800 86400
;; AUTHORITY SECTION: mydomain.com. 83298 IN NS ns1.mydomain.com. mydomain.com. 83298 IN NS ns1.my-isp.net.
;; ADDITIONAL SECTION: ns1.my-isp.net. 95665 IN A 123.123.99.99 ns1.mydomain.com. 14153 IN A 200.100.10.50
This seems OK to me. But it's the ZONE File that I think looks sorta weird.
If I run 'dig mydomain.com. ns', the return is the exact same as the above.
Any clues???
From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [GnuDIP] PING problem with GNUDip updated hostnames Date: Wed, 17 Dec 2003 06:38:16 -0700
What do you get when you do:
# ping ns1.domain.com. # ping ns2.domain.com. # ping test1.domain.com.
or
# dig mydomain.com. soa
or
# dig mydomain.com. ns
from the client machine?
I am wndering if proper access to the domain mydomain.com is in place.
[EMAIL PROTECTED] wrote:
Dear all,
I'm experiencing a problem with my DNS server. I've set up GNUDip on a Linux machine, and updating from the web via a client computer works fine. But, from the client computer, when I PING a certain newly created or newly updated hostname (ie. host1.mydomain.com) via the command prompt, the return is:
"Unknown host host1.mydomain.com."
Attached below is a sample of my zone file for mydomain.com
$ORIGIN . $TTL 86400 ; 1 day mydomain.com IN SOA ns1.mydomain.com. root.mydomain.com. ( 22 ; serial 3600 ; refresh (1 hour) 1800 ; retry (30 minutes) 604800 ; expire (1 week) 0 ; minimum (0 seconds) ) NS ns1.my-isp.net. NS ns1.mydomain.com. A 200.100.10.50 MX 0 mail.mydomain.com. $ORIGIN mydomain.com. ftp CNAME ns1 $TTL 60 ; 1 minute host1 A 200.100.10.1 $TTL 86400 ; 1 day 50.10.100.200.in-addr PTR ns1 $TTL 60 ; 1 minute host2 A 200.100.10.2 host3 A 200.100.10.3 $TTL 86400 ; 1 day localhost A 127.0.0.1 loopback CNAME localhost. mail CNAME ns1 mysqladmin A 200.100.10.50 ns1 A 200.100.10.50 ns2 A 200.100.10.51 $TTL 0 ; 0 seconds test1 A 192.168.100.100 $TTL 86400 ; 1 day www CNAME ns1 $TTL 60 ; 1 minute host4 A 200.100.10.4
NOTE ON THE ABOVE zone file:
host1, host2, host3, host4 are hostnames I added via the GNUDip web interface with admin user. I dunno why they are in the positions they are in, within the zone file. Nor do I know why there are multiple "$TTL" lines in the zone file. Is this normal or no?
I cannot ping any of host1 to host4.
Any other info should I submit for you to analyze before we can find out why I cannot ping those GNUDip added hostnames?
Best regards
Chris
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- GnuDIP Mailing List http://gnudip2.sourceforge.net/gnudip-www/#mailinglist
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- GnuDIP Mailing List http://gnudip2.sourceforge.net/gnudip-www/#mailinglist
