Dns query failed the error was dns query failed with error errorretry



DNS query failed error when an email message is stuck in the Draft folder in Exchange Server 2013

Original KB number: В 3007623

Symptoms

Assume that you have a computer that is a member of an Exchange Server 2016 or Exchange Server 2013 environment. You do not have the Register this connection’s addresses in DNS check box selected on the DNS tab of the Advanced TCP/IP Settings dialog box of TCP/IPv4. In this situation, email messages remain stuck in the Drafts folder.

Additionally, when you check the transport queue, you see an error message that resembles the following:

4.4.0 DNS query failed. The error was: DNS query failed with error ErrorRetry.

Cause

This issue occurs because the DNS service cannot be used if the Register this connection’s addresses in DNS check box is not selected in an Exchange Server 2016 or Exchange Server 2013 environment.

Resolution — Method 1: Select the Register this connection’s addresses in DNS check box

On your computer, select the Register this connection’s addresses in DNS check box on the DNS tab of the Advanced TCP/IP Settings dialog box of TCP/IPv4.

Resolution — Method 2: Enable the DNS service by using a registry key

This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.

Источник

Dns query failed the error was dns query failed with error errorretry

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

We are using MS Exchange Server 2013 CU1 on MS Windows Server 2008 Standard R2.

In queue viewer, I am getting this error for few domains only «451 4.4.0 dns query failed. The error was: DNS Query failed with error ErrorRetry»

Any because of this, We are unable to send any email to these domains,

Can someone please help to fix this.

Thanks in Advance..

All replies

According to your description,I recommend you refer to the following steps to troubleshoot the issue:

1.Please ensure that you can resolve these domains mx records.

2.Please try to use the external dns in network properties of send connector.

Hope it helps you!

Regards, Please mark it as an answer if it really helps you.

Unable to resolve MX..

You can see below the screenshot.

This is Exchange 2013, So I have also tried to change External DNS lookup but failed with below massage

Are those emails for External domain or the Same domain.

If for external domain then if your hub server is directly sending email to internet or there is any other source available.. (IF any other source there then check communication between you Exchange server and that server is there ..

If for internal then check the next hop also check if the A record for you MB server is there in your internal DNS.

Читайте также:  Error in to addresses ip address expected

This is external domain. I have all the roles installed only on single physical server and my hub server us directly sending emails to internet.

Any Help please.

So the domain in your picture resolves fine for me. If it does not, then you have a DNS issue and not an Exchange issue.

To resolve, check the DNS path that the Exchange server follows to reach the internet. Is the server that is set as its DNS server reachable? If, go to that box and do the NSLOOKUP there as well. Follow these steps until you reach the last referrer that you can access.

If it is not resolving on your last DNS server, check your firewalls beyond that server for anything interfering with port 53 traffic — for example something that validates DNS queries. If some of your DNS servers can do this lookup okay, can you change Exchange to use them? If not, then check for firewalls interfering with DNS between Exchange and your DNS servers or between different DNS servers on your forwarding path.

If you can lookup other MX records, then maybe your upstream firewalls are not coping with large DNS packets. Try turning off enhanced DNS on the Windows DNS servers with the following:

dnscmd /config /enableednsprobes 0

Note: Type a 0 (zero) and not the letter «O» after «enableednsprobes» in this command.

Источник

Dns query failed the error was dns query failed with error errorretry

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

We are using MS Exchange Server 2013 CU1 on MS Windows Server 2008 Standard R2.

In queue viewer, I am getting this error for few domains only «451 4.4.0 dns query failed. The error was: DNS Query failed with error ErrorRetry»

Any because of this, We are unable to send any email to these domains,

Can someone please help to fix this.

Thanks in Advance..

All replies

According to your description,I recommend you refer to the following steps to troubleshoot the issue:

1.Please ensure that you can resolve these domains mx records.

2.Please try to use the external dns in network properties of send connector.

Hope it helps you!

Regards, Please mark it as an answer if it really helps you.

Unable to resolve MX..

You can see below the screenshot.

This is Exchange 2013, So I have also tried to change External DNS lookup but failed with below massage

Are those emails for External domain or the Same domain.

If for external domain then if your hub server is directly sending email to internet or there is any other source available.. (IF any other source there then check communication between you Exchange server and that server is there ..

If for internal then check the next hop also check if the A record for you MB server is there in your internal DNS.

This is external domain. I have all the roles installed only on single physical server and my hub server us directly sending emails to internet.

Читайте также:  Hp laserjet m1120 scanner error 6

Any Help please.

So the domain in your picture resolves fine for me. If it does not, then you have a DNS issue and not an Exchange issue.

To resolve, check the DNS path that the Exchange server follows to reach the internet. Is the server that is set as its DNS server reachable? If, go to that box and do the NSLOOKUP there as well. Follow these steps until you reach the last referrer that you can access.

If it is not resolving on your last DNS server, check your firewalls beyond that server for anything interfering with port 53 traffic — for example something that validates DNS queries. If some of your DNS servers can do this lookup okay, can you change Exchange to use them? If not, then check for firewalls interfering with DNS between Exchange and your DNS servers or between different DNS servers on your forwarding path.

If you can lookup other MX records, then maybe your upstream firewalls are not coping with large DNS packets. Try turning off enhanced DNS on the Windows DNS servers with the following:

dnscmd /config /enableednsprobes 0

Note: Type a 0 (zero) and not the letter «O» after «enableednsprobes» in this command.

Источник

Dns query failed the error was dns query failed with error errorretry

Коллеги, добрый день!

2 — Просто, Exchange exch-01

Создаю подписку, коннекторы появляются, все ок.

Письма из вне приходят, все ок.

Проблема с исходящей почтой. Письмо встает в очередь и дальше никуда.

Имена резолвятса нормально как на самом почтовом сервере exch-01, так и на edge, DNS на этих серверах прописаны Локальные (не внешние)

Подскажите, в какую сторону смотреть

Ответы

Устал я возиться с этим сервером.

Было принято решение снести edge и поднять все с нуля. Что самое удивительное — получилось! Все работает исправно.

Почему так произошло — понятия не имею. Скорее всего из-за того, что сервер изначально был в домене и подцепил что-то политикой.

Все ответы

Сталкивался с такой же проблемой примерно год назад, не помню как решил, но вроде было связанно настройками сетевого адаптера. Ты случной не снимал эту галочку на EDGE:

У меня были ошибки? что не может зарегистрировать запись в DNS и я ее убрал и после перестали работать исходящая почта.

Этот чекбокс у меня стоит.

С DNS у меня все в порядке. Как я это проверил:

Допустим, у меня 2 сервера exch и edge

на каждом сервере выполняю 2 команды: nslookup servername , nslookup fqdn

Если возвращает ip то все работает исправно. У меня — возвращает.

Гугл мне несильно помог.

У меня есть одно предположение — Изначально edge по ошибке был введен в домен, но перед поднятием Exchange этот сервер был выведен из домена. Может быть что-то прилетело из домена из какой-то политики.

А HELLO у тебя правильно прописано? В моем случае случае причина была не очевидна и т.к. это был стенд я как-то особо не переживал по этому поводу и когда смотрел один из курсов Рудя по Exchange наткнулся на решение проблемы, вот хоть убей не помню что было:-).
Стоп, а у тебя в какой очереди застревают письма MailBox или Edge? Если на Mailbox пересоздавай подписку и проверяй что бы прошла синхронизация, как правило требуется дернуть службу.

Читайте также:  The ssl certificate error ошибка

Источник

Dns query failed the error was dns query failed with error errorretry

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

We are using MS Exchange Server 2013 CU1 on MS Windows Server 2008 Standard R2.

In queue viewer, I am getting this error for few domains only «451 4.4.0 dns query failed. The error was: DNS Query failed with error ErrorRetry»

Any because of this, We are unable to send any email to these domains,

Can someone please help to fix this.

Thanks in Advance..

All replies

According to your description,I recommend you refer to the following steps to troubleshoot the issue:

1.Please ensure that you can resolve these domains mx records.

2.Please try to use the external dns in network properties of send connector.

Hope it helps you!

Regards, Please mark it as an answer if it really helps you.

Unable to resolve MX..

You can see below the screenshot.

This is Exchange 2013, So I have also tried to change External DNS lookup but failed with below massage

Are those emails for External domain or the Same domain.

If for external domain then if your hub server is directly sending email to internet or there is any other source available.. (IF any other source there then check communication between you Exchange server and that server is there ..

If for internal then check the next hop also check if the A record for you MB server is there in your internal DNS.

This is external domain. I have all the roles installed only on single physical server and my hub server us directly sending emails to internet.

Any Help please.

So the domain in your picture resolves fine for me. If it does not, then you have a DNS issue and not an Exchange issue.

To resolve, check the DNS path that the Exchange server follows to reach the internet. Is the server that is set as its DNS server reachable? If, go to that box and do the NSLOOKUP there as well. Follow these steps until you reach the last referrer that you can access.

If it is not resolving on your last DNS server, check your firewalls beyond that server for anything interfering with port 53 traffic — for example something that validates DNS queries. If some of your DNS servers can do this lookup okay, can you change Exchange to use them? If not, then check for firewalls interfering with DNS between Exchange and your DNS servers or between different DNS servers on your forwarding path.

If you can lookup other MX records, then maybe your upstream firewalls are not coping with large DNS packets. Try turning off enhanced DNS on the Windows DNS servers with the following:

dnscmd /config /enableednsprobes 0

Note: Type a 0 (zero) and not the letter «O» after «enableednsprobes» in this command.

Источник

Оцените статью
toolgir.ru
Adblock
detector