P
Pingusman
Hi,
We have this architecture :
- Primary Domain Controller + DNS (1.1)
- Secondary Domain Controller + DNS (1.2)
- Roaming Profiles on a linux server with samba (1.3)
The two domain controller are master, for authentification it's working well
But we have a problem with the linux server, when the primary server is down, the linux server does'nt work
DNS on 1.3 :
Primary 1.1
Secondary 1.2
Example of a dns entry
DOMAIN.COM
* A 192.168.1.1
* A 192.168.1.2
This entry return randomly the primary or the secondary ip
When the primary is down :
On Windows 7 :
- First 2/3 min, ping domain.com return 1.1 or 1.2, so not working very well
- After 2/3min , ping domain.com always return 1.2 so it's working well
On Debian :
- ping domain.com always return a random ip, so it's not working good
Is there a configuration to make linux works as windows do ?
Something like filtering not responding ip in the dns request answer ?
Thanks
Continue reading...
We have this architecture :
- Primary Domain Controller + DNS (1.1)
- Secondary Domain Controller + DNS (1.2)
- Roaming Profiles on a linux server with samba (1.3)
The two domain controller are master, for authentification it's working well
But we have a problem with the linux server, when the primary server is down, the linux server does'nt work
DNS on 1.3 :
Primary 1.1
Secondary 1.2
Example of a dns entry
DOMAIN.COM
* A 192.168.1.1
* A 192.168.1.2
This entry return randomly the primary or the secondary ip
When the primary is down :
On Windows 7 :
- First 2/3 min, ping domain.com return 1.1 or 1.2, so not working very well
- After 2/3min , ping domain.com always return 1.2 so it's working well
On Debian :
- ping domain.com always return a random ip, so it's not working good
Is there a configuration to make linux works as windows do ?
Something like filtering not responding ip in the dns request answer ?
Thanks
Continue reading...