Forum Discussion
Exchange Hybrid Deployment single forest multiple email domains
Now it is giving me hard time at domain proof txt verification..
Log:
ERROR* 10233 [Client=UX, Page=DomainProof, Activity=External DNS Query, Thread=26]
http://viewdns.info/dnsrecord/?domain=domainabcd.com
System.Net.WebException: The remote server returned an error: (403) Forbidden.
at System.Net.HttpWebRequest.GetResponse()
I verified all records with ps "Test-FederatedDomainProof.ps" all looks good but wizard stay there with Waring and Next is gyred out..
Prior to this i also see this error on credentials verification screen "ERROR* 10309 [Client=UX, Thread=1] HCW8108 Hybrid Configuration Service may be limited."
Have you tried quitting out of the the HCW and starting it again? That sometimes will help.
Also, I've seen the "HCW8108 Hybrid Configuration Service may be limited" message appear a few times myself lately. Seems to be a glitch that can safely be ignored.
- PeterRisingJul 19, 2020MVP
- Jul 19, 2020
- PeterRisingJul 19, 2020MVP
If these particular domains are in Exchange Online only, then I would suggest you don't select them in the HCW, as per step 11 in the following;
- Jul 19, 2020
No Peter, this is something HCW team fix this..No such more friendly error. One thing I must mention here that there are couple of domains online (Accepted > MX>Online as well). These domains are not in On-premises Exchnage in Accepted list.
should I add them and try?
- PeterRisingJul 19, 2020MVP
- Jul 19, 2020
- PeterRisingJul 19, 2020MVP
OK, are the invalid domains configured in both Exchange On-premises, and Exchange Online?
- Jul 19, 2020
Yes, the invalid smtp domains error comes in the end when it try to configure mail flow.
- PeterRisingJul 19, 2020MVP
So does it still say "Invalid smtp domain name"? Is that the error you are referring to?
- Jul 18, 2020Yes, it passed the txt verification on second attempt for all domains and was stuck at adding federated domains for hours. I cancelled and started again ..
and now it stays with error I shown you. I think the dns lookup is forbidden/blocked and hcw can not verify...
How we can enable the dns lookup on dns servers or it will be working again after hours?
I think Microsoft should add if dns lookup fails it should check with another dns lookup site..it is just asking viewdns.info which is returning 403.