Add several IP addresses to DNS A record within Server 2016

I need to add the following IP addresses to the A record of within my Server 2016 AD domain:


What is the process to add all of these IP addresses to the DNS A record of within my Server 2016 AD domain? All of these IP addresses need to be added, not just one.
IT GuyNetwork EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Multiple A records. One per address.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cliff GaliherCommented:
And in the name of full accuracy, the IPv6 records are AAAA records.
IT GuyNetwork EngineerAuthor Commented:
When I create these A & AAAA records to I also want to create the associated pointer (PTR) records?
Introducing the "443 Security Simplified" Podcast

This new podcast puts you inside the minds of leading white-hat hackers and security researchers. Hosts Marc Laliberte and Corey Nachreiner turn complex security concepts into easily understood and actionable insights on the latest cyber security headlines and trends.

Cliff GaliherCommented:
It isn't necessary from your profile final question. Whether you choose to or not depends on your needs.
I know exactly where this question is coming from.  You don't want to create the multiple A records (at least there's no need).  Just follow the instructions in the Office 365 portal and create the CNAME record for and point it at  The records behind could be changed by MS at any time, but will always be correct.
IT GuyNetwork EngineerAuthor Commented:

Can you please refer me to an article that explains that what you are saying is true? I need to be able to show this to some other people I work with.
IT GuyNetwork EngineerAuthor Commented:

Are there any articles that explain that what footech is saying is valid?

I need to submit an article from a recognized authority before I can make a change like this within our network.
Cliff GaliherCommented:
If thus is indeed for O365 (each region has its own IP addresses)!, so I haven't bothered to compare your list to any I know), then as he said, follow the instructions IN THE PORTAL. That is about as authoritative as you can get for evidence.  And honestly, if this is for O365, I don't know where you got the list of IPs anyways. You'd have to work harder to get the list than the official instructions. Weird.
There's not much I could add to Cliff's comment.  During domain setup in Office 365 it tells you which records you should add to DNS.  Whether it's public DNS or internal (like in a split DNS scenario), there's no reason to deviate from the records it tells you to create.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.