I have hosted Wordpress website on EC2, now i have configured it with Route53 but it does not work. Can you guys please suggest what necessary changes i have to do. Below is the changes i have done. 1. Hosted a zone in Route53, mydoamin.in 2. Copy name-server to hostinger name-server (from where i purchased my domain) 3. created a record with ec2 ip (where my wordpress site is hosted) 4. changes in /etc/apache2/sites-available/000-default.conf, added ServerName mydomain.in 5. ServerAlias www.mydomain.in

If you did the step 3 well, you will be able to check the ec2 ip for using the below linux command. If not, please recheck step 1~3. how is the result? $ dig The below knowledge will help you, which records are needed in this situation. https://repost.aws/knowledge-center/route-53-create-alias-records

Route53 does not forward to my ec2 wordpress

I have hosted Wordpress website on EC2, now i have configured it with Route53 but it does not work. Can you guys please suggest what necessary changes i have to do.

Below is the changes i have done.

Hosted a zone in Route53, mydoamin.in
Copy name-server to hostinger name-server (from where i purchased my domain)
created a record with ec2 ip (where my wordpress site is hosted)
changes in /etc/apache2/sites-available/000-default.conf, added ServerName mydomain.in

                                                                                                              ServerAlias www.mydomain.in

Max Clements EXPERT
il y a un mois
Hi Faisal, you have not given enough information here for us to help you troubleshoot this. Can you provide at least your actual domain name?
Faisal
il y a un mois
Hi Max, Firstly thank you. Actually the problem was in my Laptop DNS settings. I have configured it and now it works fine.

Sujets

Calcul Réseaux et diffusion de contenu

Balises

Amazon EC2 Amazon Route 53

Langue

English

Faisal

demandé il y a un mois152 vues

1 réponse

Le plus récent
Le plus de votes
La plupart des commentaires

Réponse acceptée

If you did the step 3 well, you will be able to check the ec2 ip for using the below linux command. If not, please recheck step 1~3. how is the result?

$ dig <route 53 record>

The below knowledge will help you, which records are needed in this situation. https://repost.aws/knowledge-center/route-53-create-alias-records

EXPERT

hyp

répondu il y a un mois

EXPERT

Osvaldo Marte

vérifié il y a un mois

Faisal
il y a un mois
Hi Peer, Actually the problem was in my Laptop DNS settings. I have configured it and now it works fine. Thank you for this assistance.

Contenus pertinents

account is currently blocked and not recognized as a valid account
Yves Boah
demandé il y a un an
error 403 / cloud front
nico-HPF
demandé il y a 2 mois
S3 Error: 404 (Not Found)
Gabsi
demandé il y a 6 mois
My account is not recognized
juan ortega
demandé il y a un an
Comment résoudre l'erreur « Did not have IAM permissions to process tags on AWS::EC2::Instance resource » (Autorisations IAM indisponibles pour traiter les balises sur AWS። EC2። Instance resource) lorsque je crée une ressource AWS። EC2። Instance dans CloudFormation ?
AWS OFFICIELA mis à jour il y a 3 ans
Comment résoudre l'erreur « One or more of your origins or origin groups do not exist » (Un ou plusieurs de vos groupes d'origine ou origines n'existent pas) dans AWS CloudFormation ?
AWS OFFICIELA mis à jour il y a 2 ans
Comment résoudre l'erreur « Image does not exist » (l'image n'existe pas) lorsque le lancement de mes tâches échoue dans le cluster Amazon ECS ?
AWS OFFICIELA mis à jour il y a 2 ans
Comment résoudre l'erreur AWS Glue « The specified subnet does not have enough free addresses to satisfy the request » (Le sous-réseau spécifié ne dispose pas de suffisamment d'adresses libres pour répondre à la requête) ?
AWS OFFICIELA mis à jour il y a 2 ans