domain problem

[donkeyKICK]

Okay, maybe it is lack of sleep, but here is my problem:

I reciently replaced a server and moved a bunch of users to it. None of them resolve. They were already working, but now after restoring from backup they don't. No domains on this server work. Am I missing a setup step?

I think I did ns1.nightowlpc.com and ns2.nightowlpc.com right, but the website www.nightowlpc.com doesn't come up.

Any idea's? All IP's have stayed the same.

 

[HanSieT]

DiG displayes

[root@l33tr00tb0x ~]# dig ns1.nightowlpc.com

; <<>> DiG 9.3.3rc2 <<>> ns1.nightowlpc.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4240
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ns1.nightowlpc.com.            IN      A

;; ANSWER SECTION:
ns1.nightowlpc.com.     172800  IN      A       64.87.3.114

;; Query time: 32 msec
;; SERVER: l33tr00tb0x#53(l33tr00tb0x)
;; WHEN: Sun Jan 25 10:50:36 2009
;; MSG SIZE  rcvd: 52

[root@l33tr00tb0x ~]# dig nightowlpc.com

; <<>> DiG 9.3.3rc2 <<>> nightowlpc.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 57769
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nightowlpc.com.                        IN      A

;; Query time: 3767 msec
;; SERVER: l33tr00tb0x#53(l33tr00tb0x)
;; WHEN: Sun Jan 25 10:50:52 2009
;; MSG SIZE  rcvd: 32

[root@l33tr00tb0x ~]#

 

[donkeyKICK]

Okay, but my site doesn't come up...?

 

[HanSieT]

Its coming up now ( clicked the link in ur post)

 

[donkeyKICK]

Yea, weird, I had to make a "virtual" network card for my nameserver. I guess DA doesn't handle IPs... Or something. I sorta thought if the IP's were in DA it would work...

 

[floyd]

Yea, weird, I had to make a "virtual" network card for my nameserver. I guess DA doesn't handle IPs... Or something. I sorta thought if the IP's were in DA it would work...

DA does handle ip's and the site is still not showing up.

As you can see from HanSieT the site does not resolve to an ip. You have a dns problem of some sort.

 

[donkeyKICK]

Different issue now, now I am having trouble with APF. I installed it using ELS but for some reason it just doesn't want to work...

The virtual IP thing fixed the first issue which was a problem even when the firewall was off.

Still, I am wondering about why I needed to add eth0:0

 

[floyd]

Still, I am wondering about why I needed to add eth0:0

What do you not understand? You have to have a network listening on the ip's your nameserver records point to.

What ip is eth0? What ip is eth0:0?

 

[donkeyKICK]

Do everytime I add I'd I have to make a new virtual card?

right now I have 1 card, eth0, and a virtual one eth0:0. Is what you are saying is that I should add another one for each IP I want to use? Is there a script available that would do it for me? I seem to remember reading somewhere that DA actually can do IP stuff, and that it does it a different way.

 

[floyd]

When you add an ip through DA it creates a virtual interface. How are you adding ip's now? I don't understand what you are doing.

You should be doing this http://admin.site-helper.com/ipman.html

 

[donkeyKICK]

No, I've been doing something like method 3 offered at:

http://www.cyberciti.biz/faq/rhel-centos-fedoracore-linux-network-card-configuration/

I did it the way you posted, but it didn't make the virtual cards, so after I had to use method 3. Then it started to work.

 

[floyd]

I did it the way you posted, but it didn't make the virtual cards,

Then something is wrong with your server and you should get a server management company to look at it.

DA does not store any files in /etc/sysconfig/network-scripts/. It uses a more universal method. It stores ip information in its own directories and then starts the virtual interfaces when you add the ip and when you run /etc/rc.d/init.d/startips

 

[donkeyKICK]

I checked, and when I restarted startips it complained:

IP 64.87.3.114 already exists on eth0

I removed eth0:0 and the problem came back (page no longer came up). I'd like to know more about how this works so I can fix it. This is a clean install of Centos 5.2, and I put on custom build, spamblocker 3.1, spamassassin, clamAV and els.

 

[floyd]

I restarted startips it complained

That is because you create that ip and virtual interface already.

I removed eth0:0 and the problem came back (page no longer came up)

What problem? What page no longer came up? Do you mean the error page doesn't come up. That is good.

 

[donkeyKICK]

Sorry for the unclear post... I was really tired.

The problem is when I removed eth0:0, while the complaint went away, email and web pages stopped working.

What I did was:

removed eth0:0
restarted network (service network restart)
went to www.nightowlpc.com (page could not be displayed)
tried email (could not find server)
replaced eth0:0
restarted network (service network restart)
went to www.nightowlpc.com (page came up)
tried email (able to send and receive email)

now just in case I've done something wrong, as a backup I have 64.87.3.115 also as a nameserver, but I didn't make eth0:1 for it. So by breaking eth0:0 if I did something wrong, ns2 should have helped....

Also, I left in eth0

 

[floyd]

removed eth0:0
restarted network (service network restart)
went to www.nightowlpc.com (page could not be displayed)
tried email (could not find server)

Of course not, because eth0:0 is no longer up.

No where did you say you added the ip via directadmin.

If the ip is already added in directadmin and you restart the network (service network restart) then you also have to start startips again (service startips start). Otherwise eth0:0 or whatever the ip is supposed to be on is down.

This is what happens when admins start doing things from the command line who have not studied how directadmin does things. Yes, normally we might set up the network-scripts so that when when we restarted the network all the ip's become active again. But that is not the default way directadmin does things.

The default way is add the ip's from the directadmin interface. It starts the ip right away and adds it to its own config files so that when the server reboots directadmin, not network services, will start the ip's.

If you want to add the network-scripts too that is fine. But they have to be added via the directadmin interface as well in order for you to be able to use them via the directadmin interface, such assigning ips to other users.

If you have added the ips via directadmin and have not set up the network-scripts, then when you restart the network you also have to run startips.


http://help.directadmin.com/item.php?id=136

Do a search for startips and you will get a bunch of information.

 

[donkeyKICK]

Sorry for the delay... for some strange reason, it all of a sudden is working exacly like you described. Now DA can add and remove IP's without me having to add those eth0:? stuff (and they work!!). If the issue comes back I'll post again.

Thanks for your help.