July 6, 2015 at 9:06 am
Hello all,
Facing a new problem with my implementation.
All was installed correctly without errors. After i ve made a failover and failback this error started occurring "Name resolution not yet available" on the Listener resources.
I don't have nothing configured locally.(hosts file or lmhosts.sam)
All the resources were created without errors. Only problem is that the DNS isn't updated.
Can anyone help with this one?
Regards,
Arestas
July 6, 2015 at 12:10 pm
July 6, 2015 at 12:18 pm
Correct me if i am wrong, but all the resources should be created automatically...
Anyway i will talk with sys admin. if not present i ll pre stage all the listeners resources.
Regards,
Arestas
July 6, 2015 at 12:25 pm
can you tell us a bit more about your environment, is this a test system?
Who installed\controls the domain controller(s) and DNS server(s)?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 6, 2015 at 12:43 pm
Well its a testing system. If all goes as planned will be implemented in prod.
About the environment:
2 servers with a FCI and 1 server that will be used as DR. Replication will done with allwayson.
Each server will have 3 network cards on different vlans. (management, service and AO rep).
I don't have any access to AD or DNS. Although the account iam using to install was given "domain admin" privilege.
I am just trying to see if its something i can solve by myself.
If it was a bad configuration or something like that.
Regards,
Arestas
July 6, 2015 at 1:44 pm
Arestas (7/6/2015)
I don't have any access to AD or DNS.
A windows server failover cluster requires an Active Directory domain and a valid DNS server. It is possible to implement clustering without AD integrattion but there are limitations
Arestas (7/6/2015)
Although the account iam using to install was given "domain admin" privilege.
Ok that's why you've had no issues.
If you run the following from a command prompt on one of the cluster nodes and post the results, obfuscate any names first
ipconfig/all
set logonserver
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 7, 2015 at 3:26 am
Hello, the result of ipconfig /all is:
Windows IP Configuration
Host Name . . . . . . . . . . . . : SERVER1
Primary Dns Suffix . . . . . . . : domain.root
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.root
root
Ethernet adapter MANAGEMENT:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Eth1
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.32.14.50(Preferred) (Host IP)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 172.32.14.60(Preferred) (Cluster IP)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 172.32.14.61(Preferred) (IP of SQLInst1)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.32.14.251
DNS Servers . . . . . . . . . . . : 172.17.5.10
172.17.0.230
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter SERVICE:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Eth3
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.10.255.151(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 10.10.255.161(Preferred) (This IP is the IP configure for the listener on the primary site VLAN for SQLInst1)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter AOREP:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Eth2
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.20.255.150(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 10.20.255.161(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* :
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
Physical Address. . . . . . . . . : <some-mac.add>
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : <IPV6> (Preferred)
IPv4 Address. . . . . . . . . . . : 169.254.1.85(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : <someid>
DHCPv6 Client DUID. . . . . . . . : <some other info>
NetBIOS over Tcpip. . . . . . . . : Enabled
The result of logonserver:
LOGONSERVER=\\SOMESERVER
All the info on this isn't real but it reflects the implemented configuration.
Regards,
Arestas
July 7, 2015 at 5:58 am
so, you have a valid AD domain controller, a valid DNS infrastructure and a primary dns suffix.
So you do have access to AD and DNS, the fact you were granted domain admin is the reason you have not encountered any issues, granting domain admin is not something I would recommend doing.
Check the DNS server entries with your network admin to ensure they're correct
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 7, 2015 at 6:52 am
Already did.
For some reason only 1 entry was created per listener on dns.(instead of 2)
Already deleted the listeners (on sql server side) and asked sys admin to delete all the listener resources.
After that ive asked pre-stage the VCO.
After that ive tried to create the listeners.
Unfortunately problem persists. Need to keep digging.
From my point of view it shouldn't be a bad configuration on the SQL Servers side.
Will talk a bit more with my sysadmin to see if we can find the problem.
Regards,
Arestas
July 8, 2015 at 3:44 am
Arestas (7/7/2015)
For some reason only 1 entry was created per listener on dns.(instead of 2)
is this a multi subnet cluster?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 8, 2015 at 4:17 am
July 8, 2015 at 3:11 pm
Hello all,
It is as s a multi subnet cluster.
I've already did some read about and about some options i can alter but i didn't had time to test it.
Btw, as workaround is possible to solve this problem using hosts file? (adding the lsn entries on the client side)
Regards,
Arestas
July 9, 2015 at 3:30 am
Please post the output from the following PoSh command
Get-ClusterResource | ?{$_.ResourceType -EQ "Network Name"} |
Get-clusterparameter dnsname,creatingdc,RegisterAllProvidersIP |
ft ClusterObject,Name,Value
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 9, 2015 at 4:38 am
ClusterObject Name Value
------------- ---- -----
Cluster Name DnsName SRVCLUSTER
Cluster Name CreatingDC \\DC
Cluster Name RegisterAllProvidersIP 0
AG1_LSNSQL1 DnsName LSNSQL1
AG1_LSNSQL1 CreatingDC \\DC
AG1_LSNSQL1 RegisterAllProvidersIP 0
AG2_LSNSQL2 DnsName LSNSQL2
AG2_LSNSQL2 CreatingDC \\DC
AG2_LSNSQL2 RegisterAllProvidersIP 1
SRVDB1 DnsName SRVDB1
SRVDB1 CreatingDC \\DC
SRVDB1 RegisterAllProvidersIP 1
SRVDB2 DnsName SRVDB2
SRVDB2 CreatingDC \\DC
SRVDB2 RegisterAllProvidersIP 1
RegisterAllProvidersIP was set to 0 on lsnsql1 for test proposes. (so he doesn't creates 2 entries on the DNS.)
Anyone can point me a good document to better understand how the process of failing over and listener resource and listeners dns entries update work.
Who will update the DNS entrie? The listener VCO? who will trigger the update??
Regards,
Arestas
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply