Hostname A Entry Missing! Or Not

[nbigdog2000]

The other day i got a server, setup my dns (ns1.fragpegs.com and ns2.fragpegs.com).
I edited godaddy and this is how it look:


I waited, the DNS updated after 4 hours. Woot, i was ready to use my domain but wait. I ran into a Host name issue. My server host said they will charge me if they want to fix it, so that's my last resort.

Now, the message i get when i login is:

The server was unable to lookup an an A entry for its hostname (dog.fragpegs.com). This is generally because the entry was never added. However this could also be the result of your nameserver(s) being down. If you would like to attempt to automaticlly add the entry,click here

So i continue and

Found your hostname to be: dog.fragpegs.com
Found your short hostname to be: dog
Found your domain name to be: fragpegs.com
Found your main ip to be: 65.254.62.218
If this looks correct,

and finally

IP=65.254.62.218 Bind reloading on dog using rndc zone: [fragpegs.com] Add Complete

So my host name is dog.fragpegs.com (fragpegs.com is my main domain).

My domain doesn't work and when i do 65.254.62.218/~fragpegs, it redirects me to dog.fragpegs.com/~fragpegs/ but that doesn't work.



I have no idea what i am doing wrong.

When i restart named, i do get this:

named started ok Aug 15 17:29:33 dog named[22558]: client 65.254.62.222#33466: view localhost_resolver: received notify for zone 'fragpegs.com': not authoritative Aug 15 17:33:19 dog named[22558]: shutting down: flushing changes Aug 15 17:33:19 dog named[22558]: stopping command channel on 127.0.0.1#953 Aug 15 17:33:19 dog named[22558]: no longer listening on 127.0.0.1#53 Aug 15 17:33:19 dog named[22558]: no longer listening on 65.254.62.218#53 Aug 15 17:33:19 dog named[22558]: no longer listening on 65.254.62.219#53 Aug 15 17:33:19 dog named[22558]: no longer listening on 65.254.62.220#53 Aug 15 17:33:19 dog named[22558]: no longer listening on 65.254.62.221#53 Aug 15 17:33:19 dog named[22558]: no longer listening on 65.254.62.222#53 Aug 15 17:33:19 dog named[22558]: exiting Aug 15 17:33:19 dog named[30041]: starting BIND 9.3.3rc2 -u named Aug 15 17:33:19 dog named[30041]: found 1 CPU, using 1 worker thread Aug 15 17:33:19 dog named[30041]: loading configuration from '/etc/named.conf' Aug 15 17:33:19 dog named[30041]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 15 17:33:19 dog named[30041]: listening on IPv4 interface eth0, 65.254.62.218#53 Aug 15 17:33:19 dog named[30041]: listening on IPv4 interface eth0:1, 65.254.62.219#53 Aug 15 17:33:19 dog named[30041]: listening on IPv4 interface eth0:2, 65.254.62.220#53 Aug 15 17:33:19 dog named[30041]: listening on IPv4 interface eth0:3, 65.254.62.221#53 Aug 15 17:33:19 dog named[30041]: listening on IPv4 interface eth0:4, 65.254.62.222#53 Aug 15 17:33:19 dog named[30041]: command channel listening on 127.0.0.1#953 Aug 15 17:33:19 dog named[30041]: zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42 Aug 15 17:33:19 dog named[30041]: zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700 Aug 15 17:33:19 dog named[30041]: zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42 Aug 15 17:33:19 dog named[30041]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN/localhost_resolver: loaded serial 1997022700 Aug 15 17:33:19 dog named[30041]: zone localdomain/IN/localhost_resolver: loaded serial 42 Aug 15 17:33:19 dog named[30041]: zone localhost/IN/localhost_resolver: loaded serial 42 Aug 15 17:33:19 dog named[30041]: zone fragpegs.com/IN/internal: loaded serial 2007081500 Aug 15 17:33:19 dog named[30041]: zone sleekupload.com/IN/internal: loaded serial 2007081001 Aug 15 17:33:19 dog named[30041]: zone fragpegs.com/IN/external: loaded serial 2007081500 Aug 15 17:33:19 dog named[30041]: zone sleekupload.com/IN/external: loaded serial 2007081001 Aug 15 17:33:19 dog named[30041]: running Aug 15 17:33:19 dog named[30041]: zone sleekupload.com/IN/internal: sending notifies (serial 2007081001) Aug 15 17:33:19 dog named[30041]: zone fragpegs.com/IN/internal: sending notifies (serial 2007081500) Aug 15 17:33:19 dog named[30041]: zone fragpegs.com/IN/external: sending notifies (serial 2007081500) Aug 15 17:33:19 dog named[30041]: zone sleekupload.com/IN/external: sending notifies (serial 2007081001) Aug 15 17:33:19 dog named[30041]: client 65.254.62.222#33467: view localhost_resolver: received notify for zone 'sleekupload.com': not authoritative Aug 15 17:33:20 dog named[30041]: client 65.254.62.222#33467: view localhost_resolver: received notify for zone 'fragpegs.com': not authoritative Aug 15 17:33:20 dog named[30041]: client 65.254.62.222#33467: view localhost_resolver: received notify for zone 'fragpegs.com': not authoritative Aug 15 17:33:20 dog named[30041]: client 65.254.62.222#33467: view localhost_resolver: received notify for zone 'sleekupload.com': not authoritative

MPORTANT: Do not ignore this email.
The hostname (dog.fragpegs.com) resolves to . It should resolve to 65.254.62.218. Please be sure to correct /etc/hosts as well as the 'A' entry in zone file for the domain.

Some are all of these problems can be caused by
/etc/resolv.conf being setup incorrectly. Please check this file if you
believe everything else is correct.


You may be able to
automaticly correct this problem by using the ' Add an A entry for your
hostname ' under ' Dns Functions ' in your Web Host Manager

I also get the email above. I tried what it said and it doesn't work.

 

[MrL22]

I am getting exactly same thing as of today....

 

[MrL22]

Just found this, worked perfect for me

mv /etc/named.conf /etc/named.old
/scripts/rebuildnamedconf > /etc/named.conf
service named stop
killall -9 named
/scripts/fixndc
/scripts/fixndc

 

[nbigdog2000]

thanks, that worked.

 

[pacificw]

I'm having the same issue, (well it's ONE of many!) anyhow,
when I'm trying to run the fixndc it comes back with this error

[[email protected] etc]# /scripts/fixndc

!! fixrndc requires a syntactically correct /etc/named.conf.
!! No changes were made to /etc/named.conf. Problem was:
!! /etc/named.conf:1: '{' expected near 'section'

which I'm not sure what it is, because I've checked the
named.conf which is only half made and the named.old file
and no where in either does it have a "section"

any thoughts?

 

[CaMer0n]

I'm seeing exactly the same error in my named file.

 

[rviradia]

Got this as well, had to restore named.old, any luck with this error?

!! fixrndc requires a syntactically correct /etc/named.conf.
!! No changes were made to /etc/named.conf. Problem was:
!! /etc/named.conf:1: '{' expected near 'section'

Thanks

 

[4MOTION]

HAd the same problem, i kept the the named.old like it was.

Deleted all the contents in the named.conf

re ran the script and it worked like a charm

 

[Zi5]

Got this as well, had to restore named.old, any luck with this error?

!! fixrndc requires a syntactically correct /etc/named.conf.
!! No changes were made to /etc/named.conf. Problem was:
!! /etc/named.conf:1: '{' expected near 'section'

Thanks

mv /etc/named.conf /etc/named.old
/scripts/rebuildnamedconf
service named stop
killall -9 named
/scripts/fixndc
/scripts/fixndc

Run the comands like that
Thanks
Zi5
ايفونTrip نوكيا بوابة نوكيا Trip ايفون

برامج ايفون العاب ايفون

 

[BookMarc]

Hostname A Entry Missing!

Hi Guys,

No matter what i try i cant get rid of this.... Hostname A Entry Missing!


The server was unable to lookup an an A entry for its hostname (host.theastrologycycle.com). This is generally because the entry was never added. However this could also be the result of your nameserver(s) being down. If you would like to attempt to automatically add the entry, CLICK HERE

then ....

Adding an A entry for your hostname
Found your hostname to be: host.theastrologycycle.com
Found your short hostname to be: host
Found your domain name to be: theastrologycycle.com
Found your main ip to be: 66.197.183.229
If this looks correct,

Add The Entry

THEN...

Adding an A entry for host.theastrologycycle.com
The zone for the root domain theastrologycycle.com is missing, or could not be read. The ip address will be read from the webserver configuration and a new zone will be created for this subdomain. Sorry, a DNS entry for host.theastrologycycle.com already exists, please delete it from your nameserver configuration file (named.conf) and the zone directory first.

I tried what you guys suggested but i get the below error no matter what i try.

[[email protected] ~]# mv /etc/named.conf /etc/named.old
[[email protected] ~]# /scripts/rebuildnamedconf
named/
named/named.zero
named/localdomain.zone
named/named.broadcast
named/named.ip6.local
named/named.local
named/localhost.zone

!! fixrndc requires a syntactically correct /etc/named.conf.
!! No changes were made to /etc/named.conf. Problem was:
!! /etc/named.conf:12: option 'memstatistics-file' is not implemented

[[email protected] ~]# /scripts/rebuildnamedconf > /etc/named.conf
[[email protected] ~]# service named stop
Stopping named:                                            [  OK  ]
[[email protected] ~]# killall -9 named
named: no process killed
[[email protected] ~]# /scripts/fixndc

!! fixrndc requires a syntactically correct /etc/named.conf.
!! No changes were made to /etc/named.conf. Problem was:
!! /etc/named.conf:1: '{' expected near 'section'

[[email protected] ~]# /scripts/fixndc

!! fixrndc requires a syntactically correct /etc/named.conf.
!! No changes were made to /etc/named.conf. Problem was:
!! /etc/named.conf:1: '{' expected near 'section'

[[email protected] ~]#

my name servers are resolving fine to the ips

Ping ns2.theastrologycircle.com

Round trip time to 66.197.183.230: 70 ms
Round trip time to 66.197.183.230: 71 ms
Round trip time to 66.197.183.230: 73 ms

However when i setup a domain and call it i get

Ping

[theastrologycircle.com]

Bad destination
Bad destination
Bad destination