내용으로 건너뛰기
AWS re:Post을(를) 사용하면 다음에 동의하게 됩니다. AWS re:Post 이용 약관
AWS re:Postre:Post
re:Post 소개

잘 사용하던 도메인이 TLD propagation 에 실패하기 시작했습니다.

0

안녕하세요. Route53 에서 trade-broker.casa 라는 도메인을 구매하여 약 한달간 사용중에 있었는데, 어제부터 트래픽이 연결된 로드밸런서의 Listener에 도달하지 못하고 있습니다. TLD 에서 aws 의 네임서버에 도달하지 못하고 있는것으로 보이는데요, 도움을 요청드립니다.

  • 도메인명: trade-broker.casa
  • Hosted Zone의 네임 서버:
ns-1371.awsdns-43.org
ns-137.awsdns-17.com
ns-1587.awsdns-06.co.uk
ns-634.awsdns-15.net
  • NS 레코드의 네임 서버:
ns-1371.awsdns-43.org.
ns-137.awsdns-17.com.
ns-1587.awsdns-06.co.uk.
ns-634.awsdns-15.net.
  • dig +trace 결과:
; <<>> DiG 9.10.6 <<>> +trace trade-broker.casa
;; global options: +cmd
.			309432	IN	NS	d.root-servers.net.
.			309432	IN	NS	a.root-servers.net.
.			309432	IN	NS	f.root-servers.net.
.			309432	IN	NS	j.root-servers.net.
.			309432	IN	NS	g.root-servers.net.
.			309432	IN	NS	h.root-servers.net.
.			309432	IN	NS	c.root-servers.net.
.			309432	IN	NS	b.root-servers.net.
.			309432	IN	NS	e.root-servers.net.
.			309432	IN	NS	l.root-servers.net.
.			309432	IN	NS	m.root-servers.net.
.			309432	IN	NS	i.root-servers.net.
.			309432	IN	NS	k.root-servers.net.
.			482238	IN	RRSIG	NS 8 0 518400 20241204050000 20241121040000 61050 . TaYZSLZmM6ZzRHdku4K1sSZIR7y2dYkxVGGDLixTLzyidnluR01Q5Sn4 aX0FLf/gOg/CSlNYyRjtGwYOnCbK50/Pt0Rrm5H44dEE9K1TY9qYLtWv ydH9Nt/SOZCRhxML09ZnmF8isN8m4W/ozzdd+0IwX+sSDm+bthcLHby9 cuBbSZ1i9ezDFlcUP5czUFADVwzbeOkRPO9+YRTJDA0uRLEBd2X1jX8V 3Imtr3fAMkLA41ReWEcKvxwXextcwP22kKBb1uG/E3GVw3gxVKWWxmxT skDXLA+sHQNn1/LyH3NJuJFQ+YQi+bFb6cibz3KgEuwxDhwMdlz5Quul XQ0e2Q==
;; Received 1109 bytes from 168.126.63.1#53(168.126.63.1) in 2 ms

casa.			172800	IN	NS	a.nic.casa.
casa.			172800	IN	NS	b.nic.casa.
casa.			172800	IN	NS	c.nic.casa.
casa.			172800	IN	NS	x.nic.casa.
casa.			172800	IN	NS	y.nic.casa.
casa.			172800	IN	NS	z.nic.casa.
casa.			86400	IN	DS	39931 8 2 9870940F409B2A9D22AB87E5239F8A18B1C44A9B6528ECD318DD78D2 3EAC761B
casa.			86400	IN	RRSIG	DS 8 1 86400 20241204210000 20241121200000 61050 . hjJ1fZG3RSGf/9aeSwQOBTUUcEfCA8kMqYUtcCXKvmRyYtuSqNMmmph6 FygnB5X4e2UmVm7Cld0WbJyu//hrg8EwR8JrZjs5k+nSXoeDLUsUQ5vI wslQJxQMZfJr1RgOOcHHCZWz6A0jSZeSw4TqkioPatL6JFJBUDivT8Mu vHBtGpGeHvzD1qzYRzxCQB1D/zoYqzwzydzV6ma1kGJAHcMkqVVZNBnO Ta/MJoJMaqKe6B7nMFWmquFdrOr9MP6A3TzApa17ZQTQAvzI9UK3j4wR /BT3HLyu1ixya4ZFlUSNc+Gyie4xVio0daB9lMgxGsCm5rztHiRu7lPx eX2GEA==
;; Received 745 bytes from 192.203.230.10#53(e.root-servers.net) in 4 ms

casa.			900	IN	SOA	a.nic.casa. admin.tldns.godaddy. 1732244328 1800 300 604800 1800
casa.			900	IN	RRSIG	SOA 8 1 900 20241206025848 20241122015848 36348 casa. oam1k7JintuUHTB3FE/2FSTFGyn/bdaQIbGzuUJUBNcFFqmPXFx87Ew5 xRA5IBh0lwuaSv+l7gx/rllXF5ceeLgnLnxBu8jmcn5f2YuwxGmif8Yr Z58EWRjd5aNezwMRK2Ij3gL0kT+IdnDF/vSCJBd7AfDGT87FKAKuglha Sk3LK56eqUS/8LwIWXC24rRStythF92GEcpWcD5N2hJhHw==
qs2pu9oa97pr8mn7f2mi8mlroms81a8r.casa. 900 IN NSEC3 1 1 0 - QSICLM626KSF56TIQ6G8N019KS1BIEQP  NS SOA RRSIG DNSKEY NSEC3PARAM CDS CDNSKEY TYPE65534
qs2pu9oa97pr8mn7f2mi8mlroms81a8r.casa. 900 IN RRSIG NSEC3 8 2 900 20241201230853 20241117224923 36348 casa. d4ur2o5t/hw7wNh8QvWny6Uq5DW6+0CLiEvej8dYHzzHzfpcHXSZZgGB Cxe/Y/Dh4uuZ6O3NToULo71+/51CeU+xDARU5u5QV98YoIASDvvTdBfR wvJYPuCA15St9/70syYIYZI/7I01MWtIUdIVquf9d92ZWFv0alBg7bl3 JO3o5hD+Jq7ePDOyVVp3vMQqlgmWYMfLS+UoKjLfKWs6eA==
n1v1rdsg21fqor36lmnqe4r03gui5puf.casa. 900 IN NSEC3 1 1 0 - N3JRCEFE05O0BV15HF3VDM61857Q19AV  NS DS RRSIG
n1v1rdsg21fqor36lmnqe4r03gui5puf.casa. 900 IN RRSIG NSEC3 8 2 900 20241130215235 20241116210518 36348 casa. Xa5fQa+AyEn0QXRf16bfhn4fFspc48UzDGVJTEaCrJQ75ExV2wce7PCY 5FO+uo0p7df7lzndFHti8nZp4SmyQPC68iD/UfXGk6II8ekinftVVDTx tn3WTg1KZMU2maMtJxAVrJaAtSC+76ejzVsj7NPLnwUDdvls0Jomq5cI gaEddLU5qCE57bBva0D5SLw45PzQoHsdcTC/aQwGRXLZEQ==
6rf9ckq3dvu1qk3ql8rksjaefjaa25m8.casa. 900 IN NSEC3 1 1 0 - 6V1GJDOMGT8ACD2FEN3OQG9UDG6V8QAP  NS DS RRSIG
6rf9ckq3dvu1qk3ql8rksjaefjaa25m8.casa. 900 IN RRSIG NSEC3 8 2 900 20241203220834 20241119215300 36348 casa. XUJzbcI/xS2hbV45LSToq0XE1ibF7imC6Z6mekZJwTlDbva9kIyvT7rU z6JJMoS0mfrq329Pxw91sN0bvovvhmRl84b8wnZzlqiDAJnEB960R4Cs WMqU+REiV5+Lpat5l08vPbU0L6R8lUNR8EOYwiykFXHfxivmqltt62Jm C3NJS+R61jp+4qSvcFQafRst9NAM0ccvu3iw95QpGWH5MA==
;; Received 1168 bytes from 37.209.192.10#53(a.nic.casa) in 39 ms
주제
네트워킹 및 콘텐츠 전송
태그
아마존 루트 53도메인 이름 시스템(DNS)
언어
한국어
질문됨 일 년 전47회 조회
2개 답변
0
수락된 답변

안녕하세요.

확인하신 대로, 해당 도메인에 대한 NS 레코드 쿼리가 잘 진행되지 않는 것으로 보입니다. 이럴 경우는 주로 도메인 등록기관에서 해당 도메인 사용을 중단시켰을 가능성도 있습니다. AWS Route53 등록된 도메인 콘솔에서 상태가 이상하지는 않은 지 확인해 보시고, 지원 센터 https://support.console.aws.amazon.com/support/home 에서 기술 사례를 만들어 문의해 보시는 것이 좋을 것 같습니다.

답변함 일 년 전
0

Based on the information provided, it appears that your domain trade-broker.casa is experiencing DNS propagation issues. This can happen for various reasons, but in your case, it seems that the TLD (Top-Level Domain) servers are not properly pointing to the AWS nameservers you have configured.

The dig +trace results show that the .casa TLD is still using its own nameservers (a.nic.casa, b.nic.casa, etc.) instead of the AWS nameservers you've set up in your Route 53 hosted zone. This suggests that the changes to your domain's nameservers haven't been properly propagated or updated at the registry level.

To resolve this issue, you should take the following steps:

  1. Double-check that the nameservers listed in your Route 53 hosted zone match exactly with the nameservers set at your domain registrar. Make sure there are no typos or discrepancies.

  2. If you recently changed the nameservers, be aware that DNS changes can take up to 48 hours to fully propagate across the internet. However, since you mentioned the domain was working for about a month, this is less likely to be the cause.

  3. Contact your domain registrar (which should be Amazon Route 53 if you purchased the domain through AWS) and verify that the correct nameservers are set at the registry level. Sometimes there can be issues with the communication between the registrar and the registry.

  4. If you're certain that all the nameserver information is correct on your end, you may need to escalate the issue to AWS support. They can help investigate if there's a problem with the domain registration or DNS configuration on their side.

  5. In the meantime, you can use online DNS propagation checker tools to monitor the status of your domain's DNS across different geographic locations. This can help you determine if the issue is global or limited to certain areas.

Remember that DNS issues can be complex and may involve multiple parties (domain registrar, DNS provider, and the TLD registry). Patience and systematic checking are often required to resolve such problems.
Sources
DNS Not Propagating | AWS re:Post
Route 53 DNS Not Propagating | AWS re:Post
S53 Domain Name Service Does Not Propagate The DNS Records | AWS re:Post

답변함 일 년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

관련 콘텐츠