DNS Nameserver records not taking
I have multiple DNS zones hosted on my machine. There is what I'll call serverdomain.tld, which is the domain the server itself identifies as. I also have a small number of other domains, some on separate IPs some sharing the server IP.
I'm trying to create a nameserver record for otherdomain.tld. I have the Primary zone created. I create a new record, which has a dropdown list at the top to select the zone. I select otherdomain.tld, and enter the nameserver. I click done. I open the record and the dropdown list shows serverdomain.tld as the zone.
Anybody else seen this? Know how to fix it?
Thanks--
Greg
I have multiple DNS zones hosted on my machine. There is what I'll call serverdomain.tld, which is the domain the server itself identifies as. I also have a small number of other domains, some on separate IPs some sharing the server IP.
I'm trying to create a nameserver record for otherdomain.tld. I have the Primary zone created. I create a new record, which has a dropdown list at the top to select the zone. I select otherdomain.tld, and enter the nameserver. I click done. I open the record and the dropdown list shows serverdomain.tld as the zone.
Anybody else seen this? Know how to fix it?
Thanks--
Greg
Similar Messages
-
DNS MX Records not Propagating properly.... getting concerned.
Google may send your email out of a US server one minute and a EU one the next - global providers like this will always send email via which ever is least busy, the quickest route or the closest to the destination (depending on their MX records). It can be hit and miss until fully propagated.
Hi SpiceheadsSo Yesterday I changed the mx records of a domain to Office 365s records. Replacing/deleting a Hosted Mail trendmicro.eu MX record in the process. It has been slightly over 24hours now and the propagation of the new Office 365 MX record does not seem to be getting anywhere near completion.The users have been able to receive some emails but not all as some senders are receiving permanent failure notifications, with trendmicro.eu MX record still showing as in use and NO-DOMAIN existing.The funny thing is my ability to send emails to this domain from a Google Apps account has been inconsistent all day, one minute it works the next Google says NO-DOMAIN.I know these things can take a long time to complete but this is torture, It just doesn't seem to be holding the MX records they seem to keep switching back and forth. Maybe...
This topic first appeared in the Spiceworks Community -
Can I attach an external mic to my Macbook Air to enhance sound input for the note taking view of Word 2011 for Mac? I've tried preferences to up the volume of my sound, but I still cannot hear the recording. Any suggestions? I need to record a meeting as well as take notes so I'd like to use this tool, but the audio is not good enough.
A USB microphone can work with the Air, and I've used them before with my 11" Air. Griffin also made a product (the iMic) that will add a standard computer microphone port, connecting to your USB port. It's heyday was the time of the old iBook laptops (which also lacked a microphone in jack) but I think it's still around.
The single sound port on the 2011 models, as I recall, supports iPhone style headphone/microphone but I don't believe it will support a standard microphone input.
The built in microphone sits on the left side of the computer and I suspect wouldn't work well for picking up a lecture unless you were sitting just right in position vs. the speaker (preferably having the speaker positioned to the left and sitting really close). By design most laptop microphones presume they are going to be mainly used to record a sound coming from the person sitting at the keyboard, while for a lecture you normally would prefer it concentrate on sound coming from behind the screen. -
in an attempt to transfer FSMO roles to the 2012r2 DC the first thing I ran was dcdiag /e /c /v and after correcting some minor errors, I came upon this one in the DNS portion where a SRV record is missing and I have no idea how to fix/remove this. there's
only two DCs, 200.5 and 200.6 where the former is a Hyper-V VM running 2012r2 and the latter is a physical 2003r2 machine. I was able to successfully raise the levels to 2003 and join the 2012r2 DC. this missing SRV record does not look fatal and only warrants
a warning from dcdiag, however I would like to fix this so there's no trouble down the road. I've tried ipconfig /registerdns, but no dice. here is the message I'm concerned about:
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
the bottom portion of the DNS section that contains this message is in the RReg section and is as follows:
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
Matching CNAME record found at DNS server 192.168.200.5:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
CM-DC1-HV-NYC01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.6:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
CM-DC1-HV-NYC01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adaptersHi Ace Fekay, thank you for your help. I hope you're still with me despite my lack of responding. I needed time to move the VPN server from the DC to a separate VM and then following your instructions to disable WINS Proxy and IP routing. Some of the delay
was when I had to restart the 2003r2 server after disabling those two items since that cause DNS queries to the Internet to go unresolved with only the 2012r2 server. That's been corrected, but running dcdiag /c /e /v still gives some DNS problems. Here's
the latest run of that...
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
Starting test: DNS
See DNS test in enterprise tests section for results
......................... CM-DC-NY01 passed test DNS
See DNS test in enterprise tests section for results
......................... CM-DC1-NY01 passed test DNS
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : cmedia
Starting test: CheckSDRefDom
......................... cmedia passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... cmedia passed test CrossRefValidation
Running enterprise tests on : cmedia.local
Starting test: DNS
Test results for domain controllers:
DC: cm-dc-NY01.cmedia.local
Domain: cmedia.local
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
The OS Microsoft(R) Windows(R) Server 2003, Standard Edition (Service Pack level: 2.0) is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
MAC address is 00:00:00:00:00:00
IP Address is static
IP address: 192.168.200.6
DNS servers:
192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
192.168.200.5 (CM-DC1-NY01) [Valid]
The A host record(s) for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
TEST: Delegations (Del)
Delegation information for the zone: cmedia.local.
Delegated domain name: _msdcs.cmedia.local.
DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
Matching CNAME record found at DNS server 192.168.200.6:
406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
cm-dc-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.pdc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.5:
406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
cm-dc-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.pdc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adapters
DC: CM-DC1-NY01.cmedia.local
Domain: cmedia.local
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
The OS Microsoft Windows Server 2012 Standard (Service Pack level: 0.0) is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000010] Microsoft Hyper-V Network Adapter:
MAC address is 00:00:00:00:00:00
IP Address is static
IP address: 192.168.200.5, 0000::0000:0000:0000:0000
DNS servers:
192.168.200.5 (CM-DC1-NY01) [Valid]
192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
The A host record(s) for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found primary
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 128.9.0.107 [Invalid (unreachable)]
Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
Name: d.root-servers.net. IP: 128.8.10.90 [Invalid (unreachable)]
Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unreachable)]
Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreachable)]
Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
Name: l.root-servers.net. IP: 2001:500:3::42 [Invalid (unreachable)]
Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreachable)]
Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
TEST: Delegations (Del)
Delegation information for the zone: cmedia.local.
Delegated domain name: _msdcs.cmedia.local.
DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone cmedia.local
Test record dcdiag-test-record deleted successfully in zone cmedia.local
TEST: Records registration (RReg)
Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
Matching CNAME record found at DNS server 192.168.200.5:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
CM-DC1-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.5:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.5:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.5:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Matching CNAME record found at DNS server 192.168.200.6:
a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
CM-DC1-NY01.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.cmedia.local
Error:
Missing SRV record at DNS server 192.168.200.6:
_ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._udp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kpasswd._tcp.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.gc._msdcs.cmedia.local
Matching A record found at DNS server 192.168.200.6:
gc._msdcs.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_gc._tcp.Default-First-Site-Name._sites.cmedia.local
Matching SRV record found at DNS server 192.168.200.6:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
Warning: Record Registrations not found in some network adapters
Summary of test results for DNS servers used by the above domain controllers:
DNS server: 198.32.64.12 (l.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12 [Err
or details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:1::803f:235 [Error details: 1460 (Type: Win32 - Description: This operation ret
urned because the timeout period expired.)]
DNS server: 2001:500:2::c (c.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2::c [Error details: 1460 (Type: Win32 - Description: This operation returned b
ecause the timeout period expired.)]
DNS server: 2001:500:2d::d (d.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2d::d [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:84::b (b.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:84::b [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:503:ba3e::2:30 [Error details: 1460 (Type: Win32 - Description: This operation retu
rned because the timeout period expired.)]
DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:503:c27::2:30 [Error details: 1460 (Type: Win32 - Description: This operation retur
ned because the timeout period expired.)]
DNS server: 2001:7fd::1 (k.root-servers.net.)
2 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:7fd::1 [Error details: 1460 (Type: Win32 - Description: This operation returned bec
ause the timeout period expired.)]
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90 [Erro
r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 128.9.0.107 (b.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.9.0.107 [Erro
r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
DNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:2f::f [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:500:3::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:500:3::42 [Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]
DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:7fe::53 [Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]
DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
on the DNS server 2001:dc3::35 [Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]
DNS server: 128.63.2.53 (h.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.112.36.4 (g.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.168.200.5 (CM-DC1-NY01)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS server: 192.168.200.6 (cm-dc-NY01.cmedia.local.)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
DNS delegation for the domain _msdcs.cmedia.local. is operational on IP 192.168.200.6
DNS server: 192.203.230.10 (e.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.228.79.201 (b.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.33.4.12 (c.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.36.148.17 (i.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.5.5.241 (f.root-servers.net.)
All tests passed on this DNS server
DNS server: 192.58.128.30 (j.root-servers.net.)
All tests passed on this DNS server
DNS server: 193.0.14.129 (k.root-servers.net.)
All tests passed on this DNS server
DNS server: 198.41.0.4 (a.root-servers.net.)
All tests passed on this DNS server
DNS server: 199.7.83.42 (l.root-servers.net.)
All tests passed on this DNS server
DNS server: 199.7.91.13 (d.root-servers.net.)
All tests passed on this DNS server
DNS server: 202.12.27.33 (m.root-servers.net.)
All tests passed on this DNS server
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
Domain: cmedia.local
cm-dc-NY01 PASS PASS PASS PASS PASS WARN n/a
CM-DC1-NY01 PASS PASS PASS PASS PASS WARN n/a
......................... cmedia.local passed test DNS
Starting test: LocatorCheck
GC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
PDC Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
Time Server Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
KDC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
......................... cmedia.local passed test LocatorCheck
Starting test: FsmoCheck
GC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
PDC Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
Time Server Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
Locator Flags: 0xe00003fd
KDC Name: \\CM-DC1-NY01.cmedia.local
Locator Flags: 0xe00071fc
......................... cmedia.local passed test FsmoCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments
provided.
......................... cmedia.local passed test Intersite -
SPA 5xx and 9xx phones registering to all proxies with DNS SRV records
A weird situation -- I use DNS SRV records to prioritize the two Asterisk servers to register to (east coast vs west coast). However it seems that phones are often registering to BOTH servers and show as live on both at the same time. There seems to be little rhyme or reason as to when it occurs, but it's weird. Fortunately the phone does seem to be preferring the higher priority SRV record but I can't figure out why it is registering to both.
This happens with SPA-942s (6.1.5a) and SPA504Gs (7.4.9c).
Any ideas what makes this happen? On the surface it seems like a good thing, but functionally the phones are registering the same port numbers and only the priority server can get through firewalls with traffic for the phones. This screws up my "presence" indicators within the system.
DNS SRV RECORDS:
_sip._udp.west.server.net (for west coast customers)
Priority 10: west coast machine
Priority 20: east coast machine
_sip._udp.east.server.net (for east coast customers)
Priority 10: east coast machine
Priority 20: west coast machineWe determined this was not actually happening. There was a syncing taking place in the background that was giving the impression this was happening but it really was not.
-
Yosemite 10.10.1 - DNS cache does not clear when switching between WiFi networks
Before updating to Yosemite, DNS caches would clear when switching between WiFi networks, as they should.
For Example, when using an Exchange server, your server name might be something like mail.company.com. Outside of the corporate LAN the IP would resolve to the outside (WAN) address. When you move the laptop inside the corporate LAN, it should clear the cache so mail.company.com resolves to the internal (LAN) address. This is just one example of a dumb DNS transition not taking place switching from outside to inside (and vice versa).
Instead, OS X is holding onto the outside DNS record even when moving to the Corporate LAN. The only way to fix is to run the DNS cache command (which is MUCH more convoluted in Yosemite now), or more easily, to quickly turn off then turn on WiFi.
This is an irritation as I have to perform this action every morning, and every time I come back to my desk from offsite.Well, clearing the caches is as simple as this, no?
Clear MDNS Cache
sudo discoveryutil mdnsflushcache
Clear UDNS Cache
sudo discoveryutil udnsflushcaches
One other thing: Have you tried 10.10.2? There are many many fixes in 10.10.2 over 10.10.1. -
Command link / button action is not taking place if i use it in iterator.
Hi,
I am new to ADF, i am facing 1 issue while implementing ADF mobile browser application.
Issue: command link / button action is not taking place if i use it in iterator. its just refreshing the page it self and displaying as no records.
Scenario is i am populating the search results in results page from search page using iterator, i want to get the complete details in different page (results page -> details page) .
I have tried in different ways.like
case1:
<tr:panelGroupLayout id="pgl2" layout="vertical" styleClass="af_m_panelBase">
<tr:panelHeader text="#{classviewBundle.SEARCH_RESULTS}" id="ph1"/>
<tr:iterator id="i1" value="#{bindings.SubjectVO1.collectionModel}" var="subject"
varStatus="subIndx" rows="100">
<tr:panelBox text="#{subject.Subject} #{subject.CatalogNbr} - #{subject.CourseTitleLong}"
styleClass="af_m_listingPrimaryDetails" id="pb1">
<f:facet name="toolbar"/>
<tr:table var="ssrClass" rowBandingInterval="1" id="t1" value="#{subject.children}"
varStatus="clsIndx" rowSelection="none"
binding="#{SessionBean.subjectTable}" verticalGridVisible="true"
emptyText="No Records" width="100%">
<tr:column id="c9" sortable="false" styleClass="width:100%">
<*tr:commandLink text="Section: #{ssrClass.ClassSection}-#{ssrClass.SsrComponentLovDescr} (#{ssrClass.ClassNbr})"*
id="commandLink2" styleClass="af_m_listingLink"
*action="#{pageFlowScope.BackingBean.searchaction}"></tr:commandLink>*
//remaining code
in this case commandlink action is not able to invoke serachaction() method
case 2:
<tr:commandLink text="Section: #{ssrClass.ClassSection}-#{ssrClass.SsrComponentLovDescr} (#{ssrClass.ClassNbr})"
id="commandLink2" styleClass="af_m_listingLink"
action="classdetails}"></tr:commandLink>
in this case its not able to navigate to classdetails page.
I gave correct navigation cases and rules in taskflow,but its working fine when the command link is out of iterator only.
i tried with actionlistener too.. but no use.. please help me out of this problem .
*Update to issue:*
The actual issue is when i use command link/button in an table/iterator whose parent tag is another iterator then the action is not taking place.
the structer of my code is
< iterator1>
#command link action1
< iterator2>
#command link action2
</ iterator2>
< /iterator1>
#command link action1 is working but "#command link action2" is not...
Thanks
Shyam
Edited by: shyam on Dec 26, 2011 5:40 PMHi,
To solve my problem I used a af:foreach instead.
<af:forEach items="#{viewScope.DataBySubjectServiceBean.toArray}" var="text">
<af:commandLink text="#{text.IndTextEn}" action="indicator-selected" id="cl1">
<af:setActionListener from="#{text.IndCode}" to="#{pageFlowScope.IndicatorCodeParam}" />
</af:commandLink>
</af:forEach>
By the way you need to convert the iterator to an Array using a ManagedBean.
public Object[] toArray() {
CollectionModel cm = (CollectionModel) getEL("#{bindings.TView1.collectionModel}");
indicators = new Object[cm.getRowCount()];
for(int i=0;i<cm.getRowCount();i++){
indicators[i] = cm.getRowData(i);
return indicators;
public static Object getEL(String expr) {
FacesContext fc = FacesContext.getCurrentInstance();
return fc.getApplication().evaluateExpressionGet(fc,expr,Object.class);
Hope that helps-
Edited by: JuJuZ on Jan 3, 2012 12:23 AM
Add getEL Method -
Planned orders are not taking into account the processing time
Hi,
Could you please tell me why planned orders quantities are not based on processing time from the material master.
Materials was set before with 1 day in house production , no matter of lot size.
Based on routings I updated material master with processing time depending on lot size.
What is bottering me now is that planned orders are not taking into account processing time. (e.g. based on my processing time 1000 pce are produced in 3 days, but planned orders show me that 1000 pce are still need in 1 day , but it can not be produced in 1 day ).
what did I miss?
Thanks a lot for any information!Hello Simona
The in house production time from tab MRP 2 is lot size independent.
However, on tab work scheduling you can define a lot size dependent times.
Please observe that, if you have entered an in house production time, the processing time will not be considered. The F1 help of the field provides the following explanation:
You can define work scheduling times in the material master record in one of two ways:
Either you enter the in-house production time. If required, you can get the system to update this value from the routing.
Or you enter the setup, teardown, processing, and interoperation times. If you maintain these values, the system determines the in-house production time on the basis of lot size.
Therefore, if you want to consider the processing time, you should remove the in house processing time.
BR
Caetano -
Unable to run the application via DNS CName record.
I have Windows Server 2008R2 running an application that connects to a database via a DNS CNAME record. The application was working fine until after yesterday when it could no longer
connect to the database. The database server is up and running without any issues. You have verified remote connectivity to the database server from your workstation.
How would you troubleshoot the issue and what are the steps to resolve it?It might be that the application does not support using aliases for DNS resolution. You will need to contact your application developer/vendor for assistance.
To make sure that DNS resolution works properly from the infrastructure level, you can simply use
nslookup and make sure that the resolution is done properly.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Get Active Directory User Last Logon
Create an Active Directory test domain similar to the production one
Management of test accounts in an Active Directory production domain - Part I
Management of test accounts in an Active Directory production domain - Part II
Management of test accounts in an Active Directory production domain - Part III
Reset Active Directory user password -
Condition record not found for service net price
Hi Experts,
I have seen other posts related to this topic but didnt solve my issue. Issue is: in one system when trying to create PO for requisition, it says please enter a price for service item since "condition record not found" (because package number is wrongly taken as '00000000'. i dont know why).
In another system, again the condition record was not found but its taking some non-zero value for ESLL-NETWR and successfully creating PO.
In both the systems, coding is the same. No extra coding in user-exists. I think package is not properly determined. But in tables ESLH/ESLL, i see the values are stored in exactly the same manner as in the other system. I literally see no difference.
What could be the problem?Solved myself.
The difference was in the purchase organization data. Depending on this field there was some check: 'Ignore requisition price in PO'. This was checked in one system for a purch org due to which it was not picking the price from PR data. -
DHCP Reservation Sync and DNS Host record sync etc shown in IPAM GUI
Hello all,
I am aware of the scripts in the TechNet script center to sync DHCP leases etc to IPAM, however my question is about something else -
If you highlight an IP address (IP address inventory->select an IP), You can see fields that say: "DHCP reservation sync", "DNS PTR record sync" and "DNS host record sync" as below:
I was curious as to what these are for. Is there some built-in sync functionality for these that I perhaps have not enabled? (Don't see such options any where..)
thanks,
-RaviHi Ravi ,
The three columns tell us the information of the synchronization between IPAM server and DNS server (or DHCP server) .
Here is the detailed guide for using IPAM :
Using the IPAM Client Console :
https://technet.microsoft.com/en-us/library/jj878351.aspx#inventory
IPAM can sync DNS and DHCP records .
The IPAM database is separate from DHCP and DNS servers on our network ,and full synchronization of hosts and IP addresses between IPAM and managed DNS or DHCP servers does not occur automatically
unless we have configured automated tasks to perform this synchronization .
For detailed information ,see
DNS and DHCP record synchronization chapter in the following link :
Multi-server Management :
https://technet.microsoft.com/en-us/library/jj878329.aspx
Best Regards,
Leo
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
DNS "A" Record Preventing Networked Users from Seeing Own Website
I just set up a DNS "a" record in Server Admin to point "mail.xyz.com" to my server's internal ip (10.0.1.1).
I did this so users could stay on the network with sending and receiving mail, as opposing to going out onto the web to do so. (I have MX records on Network Solutions point "mail.xyz.com" to my server's external ip.) All of their mail clients list "mail.xyz.com" as the mail server, instead of the server's internal ip.
Trouble is, when users on the network try to access our website, "xyz.com," their browsers now return an error, saying they cannot find the server.
Any idea?
Lost count Mac OS X (10.4.9)Steve and David --
This works. I am using Server Admin. To reiterate, I
added a zone "mysite.com" and a primary server "mail"
and pointed it at my server's internal ip so my users
can stay "inside" while checking mail.
Then, to follow your suggestion, I added a machine
named "www" to zone "mysite.com" pointed to my
server's external ip.
Some questions: How can I be sure the client's
machines are going interally to the server for mail?
(When I dig it in terminal, "mail.mysite.com" returns
an "a" record for the server's internal ip -- I
suppose that is sufficient.)
Yep!
Should the primary name server for the zone be "mail"
with "www" as an added machine, or vice versa?
The primary name server just identifies the machine which is responsible for holding records for that zone (domain). Add www as a 'machine' - think of each 'machine' as a specific IP address which identifies a host, hence IP / Name partnership. Any other hostname on same IP is an 'alias' (which becomes a CNAME record in the dns file).
You say I have to do this with "any record hosted in
my public dns as a mirror." I am running three
websites from my server, all with public dns pointed
at my server. (I use the same mail
server--mail.mysite.com--for all three.) Do I need to
set up a "www" record for each website? I have no
problem accessing the sites from internal client
machines.
the basic issue is that any zone (domain) defined in your own dns becomes 'authoritative' for that domain. So when clients ask your internal dns about any zone (domain) which is defined in it, and your server does not have that record, it will respond with "no such record" and your clients must take that on face value.
Therefore, you only need to mirror records for domains which you have defined in your own dns. If you have external www.domain1.com and www.domain2.com but only have domain1.com established on your internal dns, then you only need that domain's www record mirrored. Your server will therefore not be authoritative for domain2.com and will pass all requests out to whichever external dns is authoritative for it.
-david -
Delta upload not taking place properly
Hello Everyone,
I am trying to load data from R/3 to BW.
My data target is ODS.
For the first infopkg i m doing "initialize delta update".
Now i am making changes in particular field in R/3-say i am changing the name of the proj from ABC TO XYZ.
Now I m scheduling delta infopkg.But its not displaying the change. i hv even added new record in R/3 side and then tried wid delta infopkg but its still not taking the update.
I have defined Generic delta for my datasrc.delta specific field is "PROJID" and under settings i have checked "New status for changed records".
plz help.Hi,
The SAP help on this DS recommends these steps
When you extract the documents for the first time, select the complete posting period.
SAP recommend that you carry out initialization and full upload in a number of steps in order to create smaller packages. To improve the performance, select an update via the PSA. The data is extracted in accordance with the selection criteria. In this case, the posting date of the documents is used as the selection criteria.
Initialize all future posting dates, even if the enhanced selection area does not yet contain any documents. The new documents are automatically entered by delta processing.
Carry out delta processing at regular intervals. We recommend that large utility companies carry out delta processing on a daily basis. Only documents with closed reconciliation keys can be processed.
Refer
http://help.sap.com/saphelp_nw70/helpdata/EN/87/c299397f3d11d5b3430050dadf08a4/frameset.htm
Hope this helps.
Thanks,
JituK -
Hostname/DNS "A Record" name
We are having an issue with one domain bellsouth.net we are basically getting this back from them.
12:18:29 928 MSG 10801 Recipient: [email protected]
12:18:30 888 DMN: MSG 10802 Send Failure: 521 Error - Blocked for abuse. Contact [email protected]
12:18:30 888 DMN: MSG 10802 Send Failure: 521 Error - Blocked for abuse. Contact [email protected]
12:18:59 480 MSG 10803 Analyzing result file: /media/nss/MAIL/ndhdom/wpgate/gwia/result/rae59395.645
12:18:59 480 MSG 10803 Detected error on SMTP command
12:18:59 480 MSG 10803 Command: bellsouth.net
12:18:59 480 MSG 10803 Response: 521 Error - Blocked for abuse. Contact [email protected]
When I looked up the Detected error on SMTP command, I found some information about the Hostname, currently on our server it is setup as Hostname/DNS "A Record" name: ndhc.org (according to the internet domain holder (godaddy) the host name is ndhc.org and the "A" record name is mail. What should we have in the Hostname/DNS "A Record" name field? I believe that we have tried the servername.domain name (liberxx.ndhc.org) and that failed and I think that we also tried (mail.ndhc.org) I cannot confirm that we actually have it has been awhile since we did this project, but I am just wondering if someone can help clear this up for me. Thank you. This issue only started happen with Bellsouth.net when we switched from the NetWare GWIA to the Linux GWIA is there something else that might have been missed.Originally Posted by mrosen
Hi,
dschaldedfg wrote:
>
> We are having an issue with one domain bellsouth.net we are basically
> getting this back from them.
>
> 12:18:29 928 MSG 10801 Recipient: [email protected]
> 12:18:30 888 DMN: MSG 10802 Send Failure: 521 Error - Blocked for
> abuse. Contact [email protected].
> 12:18:30 888 DMN: MSG 10802 Send Failure: 521 Error - Blocked for
> abuse. Contact [email protected].
> 12:18:59 480 MSG 10803 Analyzing result file:
> /media/nss/MAIL/ndhdom/wpgate/gwia/result/rae59395.645
> 12:18:59 480 MSG 10803 Detected error on SMTP command
> 12:18:59 480 MSG 10803 Command: bellsouth.net
> 12:18:59 480 MSG 10803 Response: 521 Error - Blocked for abuse.
> Contact [email protected].
>
> When I looked up the Detected error on SMTP command, I found some
> information about the Hostname, currently on our server it is setup as
> Hostname/DNS "A Record" name: ndhc.org (according to the internet domain
> holder (godaddy) the host name is ndhc.org and the "A" record name is
> mail. What should we have in the Hostname/DNS "A Record" name field?
mail.ndhc.org
Okay, so you think we should try putting "mail.ndhc.org" into that section (Hostname/DNS "A Record" name field) instead of what we currently have "ndhc.org"
But that error doesn't sound like it's related to DNS. It much more
sounds like you're really blacklisted for sending spam. If it's really
the hostname, then their system is giving out extremely stupid result
messages. Have you tried to contact the given email address in the
message?
I know when we first setup the system we were having an issue with the GWIA relaying, but that has since been rectified, they are the only ones that are blacklisting us, because I have checked on other sites (blacklisting websites that is) and there is nothing about our site being blacklisted. I think basically the people that are trying to receive the messages respond back saying that they never received emails from the people here at ndhc. If memory serves they have been emailed from other accounts and those go through because Bellsouth.net is not blocking those accounts, like yahoo, gmail, etc.
CU,
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
Untitled Document -
No sound recorded when taking a video using iPhone 4 running iOS 7.1.1
Symptom: Randomly, no sound recorded when taking a video. (mics are dirt free and not blocked)
What fixed it: Restarting the phone after noticing Pandora couldn't play sound either.
Note: The video recorded before the restart still has no sound, meaning the glitch prevents sound from being recorded as well as being played from apps.
Question: Why hasn't Apple come up with an update to fix the software glitch causing this? Its obvious based on discussions as far back as 2010 that this has been an issue!
Hope this helps some people who are experiencing this issue.Same problem. Now I have use Itunes alternative. Problem never with either IOS or Itunes
Maybe you are looking for
-
Sync with iCloud while charging crashes WiFi
When i try to sync to iCloud while charging my iPhone 5 my WiFi goes down, not the phone but the router. After restarting the router it works again. Syncing manually while running phone on battery and wifi everyting works fine. Anyone else got this p
-
Hi, My server: - SLES 10SP2 - Oracle 11g - unixODBC - MyODBC-unixODBC My listener.ora LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = metis-bis)(PORT = 1521)) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC
-
BAPI or program to schedule project
Hi, Any BAPI or function modue or program to schedule whole project? I have tried to run BDC of CJ20n but it is not working properly in production environment. Thanks, Harsh
-
I can´t open multiple windows in apple mail application.
When redacting a new mail, I have to close the new window and save the message if I have to look for information in the inbox. Before upgrading to Yosemite, I used to change windows simply by selecting the window that i needed in the "window" menu. N
-
Fields on the Dunning form not printed/showed after Upgrade
Dear All, my client has finished SAP Upgrade from 4.6c to ERP 6.0 version. We are using form u201CZ u201CCompanycodeu201D_Dunn_001u201D The problem is by dunning (exactly by showing the dunning correspondence) we don't see any Document Number, Doc Da